Digital broadcasting system and method of processing data in the digital broadcasting system

ABSTRACT

A digital broadcasting system and a data processing method are disclosed. A receiving system of the digital broadcasting system includes a baseband processor, a first table handler, an audio/video processor, and a content processor. The baseband processor receives a broadcast signal including mobile and main service data. The mobile service data may configure an RS frame, and the RS frame may include mobile service data for mobile audio and/or video broadcasting, a first table describing at least one channel configuration information on the mobile service data, and a second table transmitting content for data casting service. The first table handler parses the first table from the RS frame, thereby acquiring at least one channel configuration information on the mobile service data. The audio/video processor extracts mobile service data of a mobile broadcast program requested for viewing from the RS frame, by referring to the channel configuration information of the first table handler, and decodes the extracted mobile service data, thereby outputting the decoded data to a speaker and/or a display screen. And, the content processor parses the second table from the RS frame to extract content, and processes the extracted content based upon an information associated with the extracted content.

This application claims the benefit of U.S. Provisional PatentApplication No. 60/957,714, filed on Aug. 24, 2007, U.S. ProvisionalPatent Application No. 60/974,084, filed on Sep. 21, 2007, U.S.Provisional Patent Application No. 60/977,379, filed on Oct. 4, 2007,U.S. Provisional Patent Application No. 61/044,504 filed on Apr. 13,2008, U.S. Provisional Patent Application No. 61/076,686, filed on Jun.29, 2008 and Korean Patent Application No. 10-2008-0082427, filed onAug. 22, 2008, which are hereby incorporated by reference as if fullyset forth herein.

BACKGROUND OF THE INVENTION

1. The Field

The present invention relates to a digital broadcasting system and amethod of processing data in a digital broadcasting system fortransmitting and receiving digital broadcast signals.

2. Discussion of the Related Art

The Vestigial Sideband (VSB) transmission mode, which is adopted as thestandard for digital broadcasting in North America and the Republic ofKorea, is a system using a single carrier method. Therefore, thereceiving performance of the digital broadcast receiving system may bedeteriorated in a poor channel environment. Particularly, sinceresistance to changes in channels and noise is more highly required whenusing portable and/or mobile broadcast receivers, the receivingperformance may be even more deteriorated when transmitting mobileservice data by the VSB transmission mode.

SUMMARY OF THE INVENTION

Accordingly, an object of the present invention is to provide a digitalbroadcasting system and a data processing method that are highlyresistant to channel changes and noise.

Another object of the present invention is to provide a digitalbroadcasting system and a data processing method that can receive andprocess content for a data casting service, which is transmitted in atable format.

To achieve these objects and other advantages and in accordance with thepurpose of the invention, as embodied and broadly described herein, adigital broadcast receiving system includes a baseband processor, afirst table handler, an audio/video processor, and a content processor.The baseband processor receives a broadcast signal including mobileservice data and main service data. Herein, the mobile service data mayconfigure an RS frame, and the RS frame may include mobile service datafor at least one of mobile audio broadcasting and mobile videobroadcasting, a first table describing at least one channelconfiguration information on the mobile service data, and a second tabletransmitting content for data casting service. The first table handlerparses the first table from the RS frame, thereby acquiring at least onechannel configuration information on the mobile service data. Theaudio/video processor extracts mobile service data of a mobile broadcastprogram requested for viewing from the RS frame, by referring to thechannel configuration information of the first table handler, anddecodes the extracted mobile service data, thereby outputting thedecoded data to at least one of a speaker and a display screen. And, thecontent processor parses the second table from the RS frame, so as toextract a content, and processes the extracted content based upon aninformation associated with the extracted content.

Herein, at least one data group configuring the RS frame may eachinclude a plurality of known data sequences, wherein a signalinginformation region may be included between a first known data sequenceand a second known data sequence, and wherein the signaling informationregion may include transmission parameter channel (TPC) signaling dataand fast information channel (FIC) signaling data.

The baseband processor may further include a known sequence detectordetecting known data sequences included in the data group. Herein, thedetected known data sequence may be used for demodulation andchannel-equalization of the mobile service data.

The information associated with the content may be included in at leastone of the first table and the second table.

Also, the information associated with the content may includesynchronization identification information identifying a synchronizationstatus with a mobile broadcast program.

Herein, when the synchronization identification information indicatesthe content extracted from the second table to be in synchronizationwith the mobile broadcast program, the content processor may eitherimmediately process the content based upon a display information fromthe information associated with the corresponding content, therebyoutputting the processed content to a display screen, or store theextracted content and process the corresponding content at a designatedtrigger time, thereby outputting the processed content to the displayscreen.

Alternatively, when the synchronization identification informationindicates the content extracted from the second table to not be insynchronization with the mobile broadcast program, the content processormay store the extracted content and delete the stored content when acontent deletion time is expired.

In another aspect of the present invention, a data processing method ofa digital broadcast receiving system includes the steps of receiving abroadcast signal including mobile service data and main service data,wherein the mobile service data configures an RS frame, and wherein theRS frame include mobile service data for at least one of mobile audiobroadcasting and mobile video broadcasting, a first table describing atleast one channel configuration information on the mobile service data,and a second table transmitting content for data casting service,parsing the first table from the RS frame, thereby acquiring at leastone channel configuration information on the mobile service data,extracting mobile service data of a mobile broadcast program requestedfor viewing from the RS frame, by referring to the channel configurationinformation of the first table handler, and decoding the extractedmobile service data, thereby outputting the decoded data to at least oneof a speaker and a display screen, and parsing the second table from theRS frame, so as to extract a content, and processing the extractedcontent based upon an information associated with the extracted content.

Additional advantages, objects, and features of the invention may berealized and attained by the structure particularly pointed out in thewritten description as well as the appended drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a block diagram showing a general structure of adigital broadcasting receiving system according to an embodiment of thepresent invention;

FIG. 2 illustrates an exemplary structure of a data group according tothe present invention;

FIG. 3 illustrates an RS frame according to an embodiment of the presentinvention;

FIG. 4 illustrates an example of an MH frame structure for transmittingand receiving mobile service data according to the present invention;

FIG. 5 illustrates an example of a general VSB frame structure;

FIG. 6 illustrates a example of mapping positions of the first 4 slotsof a sub-frame in a spatial area with respect to a VSB frame;

FIG. 7 illustrates a example of mapping positions of the first 4 slotsof a sub-frame in a chronological (or time) area with respect to a VSBframe;

FIG. 8 illustrates an exemplary order of data groups being assigned toone of 5 sub-frames configuring an MH frame according to the presentinvention;

FIG. 9 illustrates an example of a single parade being assigned to an MHframe according to the present invention;

FIG. 10 illustrates an example of 3 parades being assigned to an MHframe according to the present invention;

FIG. 11 illustrates an example of the process of assigning 3 paradesshown in FIG. 10 being expanded to 5 sub-frames within an MH frame;

FIG. 12 illustrates a data transmission structure according to anembodiment of the present invention, wherein signaling data are includedin a data group so as to be transmitted;

FIG. 13 illustrates a hierarchical signaling structure according to anembodiment of the present invention;

FIG. 14 illustrates an exemplary FIC body format according to anembodiment of the present invention;

FIG. 15 illustrates an exemplary bit stream syntax structure withrespect to an FIC segment according to an embodiment of the presentinvention;

FIG. 16 illustrates an exemplary bit stream syntax structure withrespect to a payload of an FIC segment according to the presentinvention, when an FIC type field value is equal to ‘0’;

FIG. 17 illustrates an exemplary bit stream syntax structure of aservice map table according to the present invention;

FIG. 18 illustrates an exemplary bit stream syntax structure of an MHaudio descriptor according to the present invention;

FIG. 19 illustrates an exemplary bit stream syntax structure of an MHRTP payload type descriptor according to the present invention;

FIG. 20 illustrates an exemplary bit stream syntax structure of an MHcurrent event descriptor according to the present invention;

FIG. 21 illustrates an exemplary bit stream syntax structure of an MHnext event descriptor according to the present invention;

FIG. 22 illustrates an exemplary bit stream syntax structure of an MHsystem time descriptor according to the present invention;

FIG. 23 illustrates segmentation and encapsulation processes of aservice map table according to the present invention;

FIG. 24 illustrates a flow chart for accessing a virtual channel usingFIC and SMT according to the present invention;

FIG. 25 illustrates an exemplary bit stream syntax structure of an EMTaccording to another embodiment of the present invention;

FIG. 26 illustrates an exemplary syntax structure of a data castingtable according to a first embodiment of the present invention;

FIG. 27 illustrates an exemplary syntax structure of a data castdescriptor according to a second embodiment of the present invention;

FIG. 28 illustrates an exemplary syntax structure of a data castingtable according to a second embodiment of the present invention;

FIG. 29 to FIG. 33 respectively illustrate exemplary data castingservice screens according to the present invention;

FIG. 34 illustrates a flow chart showing process steps of a data castingservice method according to the present invention; and

FIG. 35 illustrates a block view showing a structure of a digitalbroadcast receiving system for data casting service according to anotherembodiment of the present invention.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

Reference will now be made in detail to the preferred embodiments of thepresent invention, examples of which are illustrated in the accompanyingdrawings. Hereinafter, the preferred embodiment of the present inventionwill be described with reference to the accompanying drawings. At thistime, it is to be understood that the following detailed description ofthe present invention illustrated in the drawings and described withreference to the drawings are exemplary and explanatory and technicalspirits of the present invention and main features and operation of thepresent invention will not be limited by the following detaileddescription.

DEFINITION OF THE TERMS USED IN THE PRESENT INVENTION

Although general terms, which are widely used considering functions inthe present invention, have been selected in the present invention, theymay be changed depending on intention of those skilled in the art,practices, or new technology. Also, in specific case, the applicant mayoptionally select the terms. In this case, the meaning of the terms willbe described in detail in the description part of the invention.Therefore, it is to be understood that the terms should be defined basedupon their meaning not their simple title and the whole description ofthe present invention.

Among the terms used in the description of the present invention, mainservice data correspond to data that can be received by a fixedreceiving system and may include audio/video (A/V) data. Morespecifically, the main service data may include A/V data of highdefinition (HD) or standard definition (SD) levels and may also includediverse data types required for data broadcasting. Also, the known datacorrespond to data pre-known in accordance with a pre-arranged agreementbetween the receiving system and the transmitting system.

Additionally, among the terms used in the present invention, “MH”corresponds to the initials of “mobile” and “handheld” and representsthe opposite concept of a fixed-type system. Furthermore, the MH servicedata may include at least one of mobile service data and handheldservice data, and will also be referred to as “mobile service data” forsimplicity. Herein, the mobile service data not only correspond to MHservice data but may also include any type of service data with mobileor portable characteristics. Therefore, the mobile service dataaccording to the present invention are not limited only to the MHservice data.

The above-described mobile service data may correspond to data havinginformation, such as program execution files, stock information, and soon, and may also correspond to A/V data. Most particularly, the mobileservice data may correspond to A/V data having lower resolution andlower data rate as compared to the main service data. For example, if anA/V codec that is used for a conventional main service corresponds to aMPEG-2 codec, a MPEG-4 advanced video coding (AVC) or scalable videocoding (SVC) having better image compression efficiency may be used asthe A/V codec for the mobile service. Furthermore, any type of data maybe transmitted as the mobile service data. For example, transportprotocol expert group (TPEG) data for broadcasting real-timetransportation information may be transmitted as the main service data.

Also, a data service using the mobile service data may include weatherforecast services, traffic information services, stock informationservices, viewer participation quiz programs, real-time polls andsurveys, interactive education broadcast programs, gaming services,services providing information on synopsis, character, background music,and filming sites of soap operas or series, services providinginformation on past match scores and player profiles and achievements,and services providing information on product information and programsclassified by service, medium, time, and theme enabling purchase ordersto be processed. Herein, the present invention is not limited only tothe services mentioned above.

In the present invention, the transmitting system provides backwardcompatibility in the main service data so as to be received by theconventional receiving system. Herein, the main service data and themobile service data are multiplexed to the same physical channel andthen transmitted.

Furthermore, the transmitting system according to the present inventionperforms additional encoding on the mobile service data and inserts thedata already known by the receiving system and transmitting system(e.g., known data), thereby transmitting the processed data.

Therefore, when using the transmitting system according to the presentinvention, the receiving system may receive the mobile service dataduring a mobile state and may also receive the mobile service data withstability despite various distortion and noise occurring within thechannel.

Receiving System

FIG. 1 illustrates a block diagram showing a general structure of areceiving system according to an embodiment of the present invention.The receiving system according to the present invention includes abaseband processor 100, a management processor 200, and a presentationprocessor 300.

The baseband processor 100 includes an operation controller 110, a tuner120, a demodulator 130, an equalizer 140, a known sequence detector (orknown data detector) 150, a block decoder (or mobile handheld blockdecoder) 160, a primary Reed-Solomon (RS) frame decoder 170, a secondaryRS frame decoder 180, and a signaling decoder 190.

The operation controller 110 controls the operation of each blockincluded in the baseband processor 100.

By tuning the receiving system to a specific physical channel frequency,the tuner 120 enables the receiving system to receive main service data,which correspond to broadcast signals for fixed-type broadcast receivingsystems, and mobile service data, which correspond to broadcast signalsfor mobile broadcast receiving systems. At this point, the tunedfrequency of the specific physical channel is down-converted to anintermediate frequency (IF) signal, thereby being outputted to thedemodulator 130 and the known sequence detector 140. The passbanddigital IF signal being outputted from the tuner 120 may only includemain service data, or only include mobile service data, or include bothmain service data and mobile service data.

The demodulator 130 performs self-gain control, carrier recovery, andtiming recovery processes on the passband digital IF signal inputtedfrom the tuner 120, thereby translating the IF signal to a basebandsignal. Then, the demodulator 130 outputs the baseband signal to theequalizer 140 and the known sequence detector 150. The demodulator 130uses the known data symbol sequence inputted from the known sequencedetector 150 during the timing and/or carrier recovery, therebyenhancing the demodulating performance.

The equalizer 140 compensates channel-associated distortion included inthe signal demodulated by the demodulator 130. Then, the equalizer 140outputs the distortion-compensated signal to the block decoder 160. Byusing a known data symbol sequence inputted from the known sequencedetector 150, the equalizer 140 may enhance the equalizing performance.Furthermore, the equalizer 140 may receive feed-back on the decodingresult from the block decoder 160, thereby enhancing the equalizingperformance.

The known sequence detector 150 detects known data place (or position)inserted by the transmitting system from the input/output data (i.e.,data prior to being demodulated or data being processed with partialdemodulation). Then, the known sequence detector 150 outputs thedetected known data position information and known data sequencegenerated from the detected position information to the demodulator 130and the equalizer 140. Additionally, in order to allow the block decoder160 to identify the mobile service data that have been processed withadditional encoding by the transmitting system and the main service datathat have not been processed with any additional encoding, the knownsequence detector 150 outputs such corresponding information to theblock decoder 160.

If the data channel-equalized by the equalizer 140 and inputted to theblock decoder 160 correspond to data processed with both block-encodingand trellis-encoding by the transmitting system (i.e., data within theRS frame, signaling data), the block decoder 160 may performtrellis-decoding and block-decoding as inverse processes of thetransmitting system. On the other hand, if the data channel-equalized bythe equalizer 140 and inputted to the block decoder 160 correspond todata processed only with trellis-encoding and not block-encoding by thetransmitting system (i.e., main service data), the block decoder 160 mayperform only trellis-decoding.

The signaling decoder 190 decoded signaling data that have beenchannel-equalized and inputted from the equalizer 140. It is assumedthat the signaling data inputted to the signaling decoder 190 correspondto data processed with both block-encoding and trellis-encoding by thetransmitting system. Examples of such signaling data may includetransmission parameter channel (TPC) data and fast information channel(FIC) data. Each type of data will be described in more detail in alater process. The FIC data decoded by the signaling decoder 190 areoutputted to the FIC handler 215. And, the TPC data decoded by thesignaling decoder 190 are outputted to the TPC handler 214.

Meanwhile, according to the present invention, the transmitting systemuses RS frames by encoding units. Herein, the RS frame may be dividedinto a primary RS frame and a secondary RS frame. However, according tothe embodiment of the present invention, the primary RS frame and thesecondary RS frame will be divided based upon the level of importance ofthe corresponding data.

The primary RS frame decoder 170 receives the data outputted from theblock decoder 160. At this point, according to the embodiment of thepresent invention, the primary RS frame decoder 170 receives only themobile service data that have been Reed-Solomon (RS)-encoded and/orcyclic redundancy check (CRC)-encoded from the block decoder 160.Herein, the primary RS frame decoder 170 receives only the mobileservice data and not the main service data. The primary RS frame decoder170 performs inverse processes of an RS frame encoder (not shown)included in the transmitting system, thereby correcting errors existingwithin the primary RS frame. More specifically, the primary RS framedecoder 170 forms a primary RS frame by grouping a plurality of datagroups and, then, correct errors in primary RS frame units. In otherwords, the primary RS frame decoder 170 decodes primary RS frames, whichare being transmitted for actual broadcast services.

Additionally, the secondary RS frame decoder 180 receives the dataoutputted from the block decoder 160. At this point, according to theembodiment of the present invention, the secondary RS frame decoder 180receives only the mobile service data that have been RS-encoded and/orCRC-encoded from the block decoder 160. Herein, the secondary RS framedecoder 180 receives only the mobile service data and not the mainservice data. The secondary RS frame decoder 180 performs inverseprocesses of an RS frame encoder (not shown) included in thetransmitting system, thereby correcting errors existing within thesecondary RS frame. More specifically, the secondary RS frame decoder180 forms a secondary RS frame by grouping a plurality of data groupsand, then, correct errors in secondary RS frame units. In other words,the secondary RS frame decoder 180 decodes secondary RS frames, whichare being transmitted for mobile audio service data, mobile videoservice data, guide data, and so on.

Meanwhile, the management processor 200 according to an embodiment ofthe present invention includes an MH physical adaptation processor 210,an IP network stack 220, a streaming handler 230, a system information(SI) handler 240, a file handler 250, a multi-purpose internet mainextensions (MIME) type handler 260, and an electronic service guide(ESG) handler 270, and an ESG decoder 280, and a storage unit 290.

The MH physical adaptation processor 210 includes a primary RS framehandler 211, a secondary RS frame handler 212, an MH transport packet(TP) handler 213, a TPC handler 214, an FIC handler 215, and a physicaladaptation control signal handler 216.

The TPC handler 214 receives and processes baseband information requiredby modules corresponding to the MH physical adaptation processor 210.The baseband information is inputted in the form of TPC data. Herein,the TPC handler 214 uses this information to process the FIC data, whichhave been sent from the baseband processor 100.

The TPC data are transmitted from the transmitting system to thereceiving system via a predetermined region of a data group. The TPCdata may include at least one of an MH ensemble ID, an MH sub-framenumber, a total number of MH groups (TNoG), an RS frame continuitycounter, a column size of RS frame (N), and an FIC version number.

Herein, the MH ensemble ID indicates an identification number of each MHensemble carried in the corresponding channel.

The MH sub-frame number signifies a number identifying the MH sub-framenumber in an MH frame, wherein each MH group associated with thecorresponding MH ensemble is transmitted.

The TNoG represents the total number of MH groups including all of theMH groups belonging to all MH parades included in an MH sub-frame.

The RS frame continuity counter indicates a number that serves as acontinuity counter of the RS frames carrying the corresponding MHensemble. Herein, the value of the RS frame continuity counter shall beincremented by 1 modulo 16 for each successive RS frame.

N represents the column size of an RS frame belonging to thecorresponding MH ensemble. Herein, the value of N determines the size ofeach MH TP.

Finally, the FIC version number signifies the version number of an FICcarried on the corresponding physical channel.

As described above, diverse TPC data are inputted to the TPC handler 214via the signaling decoder 190 shown in FIG. 1. Then, the received TPCdata are processed by the TPC handler 214. The received TPC data mayalso be used by the FIC handler 215 in order to process the FIC data.

The FIC handler 215 processes the FIC data by associating the FIC datareceived from the baseband processor 100 with the TPC data.

The physical adaptation control signal handler 216 collects FIC datareceived through the FIC handler 215 and SI data received through RSframes. Then, the physical adaptation control signal handler 216 usesthe collected FIC data and SI data to configure and process IP datagramsand access information of mobile broadcast services. Thereafter, thephysical adaptation control signal handler 216 stores the processed IPdatagrams and access information to the storage unit 290.

The primary RS frame handler 211 identifies primary RS frames receivedfrom the primary RS frame decoder 170 of the baseband processor 100 foreach row unit, so as to configure an MH TP. Thereafter, the primary RSframe handler 211 outputs the configured MH TP to the MH TP handler 213.

The secondary RS frame handler 212 identifies secondary RS framesreceived from the secondary RS frame decoder 180 of the basebandprocessor 100 for each row unit, so as to configure an MH TP.Thereafter, the secondary RS frame handler 212 outputs the configured MHTP to the MH TP handler 213.

The MH transport packet (TP) handler 213 extracts a header from each MHTP received from the primary RS frame handler 211 and the secondary RSframe handler 212, thereby determining the data included in thecorresponding MH TP. Then, when the determined data correspond to SIdata (i.e., SI data that are not encapsulated to IP datagrams), thecorresponding data are outputted to the physical adaptation controlsignal handler 216. Alternatively, when the determined data correspondto an IP datagram, the corresponding data are outputted to the IPnetwork stack 220.

The IP network stack 220 processes broadcast data that are beingtransmitted in the form of IP datagrams. More specifically, the IPnetwork stack 220 processes data that are inputted via user datagramprotocol (UDP), real-time transport protocol (RTP), real-time transportcontrol protocol (RTCP), asynchronous layered coding/layered codingtransport (ALC/LCT), file delivery over unidirectional transport(FLUTE), and so on. Herein, when the processed data correspond tostreaming data, the corresponding data are outputted to the streaminghandler 230. And, when the processed data correspond to data in a fileformat, the corresponding data are outputted to the file handler 250.Finally, when the processed data correspond to SI-associated data, thecorresponding data are outputted to the SI handler 240.

The SI handler 240 receives and processes SI data having the form of IPdatagrams, which are inputted to the IP network stack 220.

When the inputted data associated with SI correspond to MIME-type data,the inputted data are outputted to the MIME-type handler 260.

The MIME-type handler 260 receives the MIME-type SI data outputted fromthe SI handler 240 and processes the received MIME-type SI data.

The file handler 250 receives data from the IP network stack 220 in anobject format in accordance with the ALC/LCT and FLUTE structures. Thefile handler 250 groups the received data to create a file format.Herein, when the corresponding file includes ESG, the file is outputtedto the ESG handler 270. On the other hand, when the corresponding fileincludes data for other file-based services, the file is outputted tothe presentation controller 330 of the presentation processor 300.

The ESG handler 270 processes the ESG data received from the filehandler 250 and stores the processed ESG data to the storage unit 290.Alternatively, the ESG handler 270 may output the processed ESG data tothe ESG decoder 280, thereby allowing the ESG data to be used by the ESGdecoder 280.

The storage unit 290 stores the system information (SI) received fromthe physical adaptation control signal handler 210 and the ESG handler270 therein. Thereafter, the storage unit 290 transmits the stored SIdata to each block.

The ESG decoder 280 either recovers the ESG data and SI data stored inthe storage unit 290 or recovers the ESG data transmitted from the ESGhandler 270. Then, the ESG decoder 280 outputs the recovered data to thepresentation controller 330 in a format that can be outputted to theuser.

The streaming handler 230 receives data from the IP network stack 220,wherein the format of the received data are in accordance with RTPand/or RTCP structures. The streaming handler 230 extracts audio/videostreams from the received data, which are then outputted to theaudio/video (A/V) decoder 310 of the presentation processor 300. Theaudio/video decoder 310 then decodes each of the audio stream and videostream received from the streaming handler 230.

The display module 320 of the presentation processor 300 receives audioand video signals respectively decoded by the A/V decoder 310. Then, thedisplay module 320 provides the received audio and video signals to theuser through a speaker and/or a screen.

The presentation controller 330 corresponds to a controller managingmodules that output data received by the receiving system to the user.

The channel service manager 340 manages an interface with the user,which enables the user to use channel-based broadcast services, such aschannel map management, channel service connection, and so on.

The application manager 350 manages an interface with a user using ESGdisplay or other application services that do not correspond tochannel-based services.

Data Format Structure

Meanwhile, the data structure used in the mobile broadcasting technologyaccording to the embodiment of the present invention may include a datagroup structure and an RS frame structure, which will now be describedin detail.

FIG. 2 illustrates an exemplary structure of a data group according tothe present invention.

FIG. 2 shows an example of dividing a data group according to the datastructure of the present invention into 10 MH blocks (i.e., MH block 1(B1) to MH block 10 (B10)). In this example, each MH block has thelength of 16 segments. Referring to FIG. 2, only the RS parity data areallocated to portions of the previous 5 segments of the MH block 1 (B1)and the next 5 segments of the MH block 10 (B10). The RS parity data areexcluded in regions A to D of the data group.

More specifically, when it is assumed that one data group is dividedinto regions A, B, C, and D, each MH block may be included in any one ofregion A to region D depending upon the characteristic of each MH blockwithin the data group. Herein, the data group is divided into aplurality of regions to be used for different purposes. Morespecifically, a region of the main service data having no interferenceor a very low interference level may be considered to have a moreresistant (or stronger) receiving performance as compared to regionshaving higher interference levels. Additionally, when using a systeminserting and transmitting known data in the data group, wherein theknown data are known based upon an agreement between the transmittingsystem and the receiving system, and when consecutively long known dataare to be periodically inserted in the mobile service data, the knowndata having a predetermined length may be periodically inserted in theregion having no interference from the main service data (i.e., a regionwherein the main service data are not mixed). However, due tointerference from the main service data, it is difficult to periodicallyinsert known data and also to insert consecutively long known data to aregion having interference from the main service data.

Referring to FIG. 2, MH block 4 (B4) to MH block 7 (B7) correspond toregions without interference of the main service data. MH block 4 (B4)to MH block 7 (B7) within the data group shown in FIG. 2 correspond to aregion where no interference from the main service data occurs. In thisexample, a long known data sequence is inserted at both the beginningand end of each MH block. In the description of the present invention,the region including MH block 4 (B4) to MH block 7 (B7) will be referredto as “region A (=B4+B5+B6+B7)”. As described above, when the data groupincludes region A having a long known data sequence inserted at both thebeginning and end of each MH block, the receiving system is capable ofperforming equalization by using the channel information that can beobtained from the known data. Therefore, the strongest equalizingperformance may be yielded (or obtained) from one of region A to regionD.

In the example of the data group shown in FIG. 2, MH block 3 (B3) and MHblock 8 (B8) correspond to a region having little interference from themain service data. Herein, a long known data sequence is inserted inonly one side of each MH block B3 and B8. More specifically, due to theinterference from the main service data, a long known data sequence isinserted at the end of MH block 3 (B3), and another long known datasequence is inserted at the beginning of MH block 8 (B8). In the presentinvention, the region including MH block 3 (B3) and MH block 8 (B8) willbe referred to as “region B (=B3+B8)”. As described above, when the datagroup includes region B having a long known data sequence inserted atonly one side (beginning or end) of each MH block, the receiving systemis capable of performing equalization by using the channel informationthat can be obtained from the known data. Therefore, a strongerequalizing performance as compared to region C/D may be yielded (orobtained).

Referring to FIG. 2, MH block 2 (B2) and MH block 9 (B9) correspond to aregion having more interference from the main service data as comparedto region B. A long known data sequence cannot be inserted in any sideof MH block 2 (B2) and MH block 9 (B9). Herein, the region including MHblock 2 (B2) and MH block 9 (B9) will be referred to as “region C(=B2+B9)”.

Finally, in the example shown in FIG. 2, MH block 1 (B1) and MH block 10(B10) correspond to a region having more interference from the mainservice data as compared to region C. Similarly, a long known datasequence cannot be inserted in any side of MH block 1 (B1) and MH block10 (B10). Herein, the region including MH block 1 (B1) and MH block 10(B10) will be referred to as “region D (=B1+B10)”. Since region C/D isspaced further apart from the known data sequence, when the channelenvironment undergoes frequent and abrupt changes, the receivingperformance of region C/D may be deteriorated.

Additionally, the data group includes a signaling information areawherein signaling information is assigned (or allocated).

In the present invention, the signaling information area may start fromthe 1^(st) segment of the 4^(th) MH block (B4) to a portion of the2^(nd) segment. According to an embodiment of the present invention, thesignaling information area for inserting signaling information may startfrom the 1^(st) segment of the 4^(th) MH block (B4) to a portion of the2^(nd) segment.

More specifically, 276 (=207+69) bytes of the 4^(th) MH block (B4) ineach data group are assigned as the signaling information area. In otherwords, the signaling information area consists of 207 bytes of the1^(st) segment and the first 69 bytes of the 2^(nd) segment of the4^(th) MH block (B4). The 1^(st) segment of the 4^(th) MH block (B4)corresponds to the 17^(th) or 173^(rd) segment of a VSB field.

Herein, the signaling information may be identified by two differenttypes of signaling channels: a transmission parameter channel (TPC) anda fast information channel (FIC).

Herein, the TPC data may include at least one of an MH ensemble ID, anMH sub-frame number, a total number of MH groups (TNoG), an RS framecontinuity counter, a column size of RS frame (N), and an FIC versionnumber. However, the TPC data (or information) presented herein aremerely exemplary. And, since the adding or deleting of signalinginformation included in the TPC data may be easily adjusted and modifiedby one skilled in the art, the present invention will, therefore, not belimited to the examples set forth herein. Furthermore, the FIC isprovided to enable a fast service acquisition of data receivers, and theFIC includes cross layer information between the physical layer and theupper layer(s).

For example, when the data group includes 6 known data sequences, asshown in FIG. 2, the signaling information area is located between thefirst known data sequence and the second known data sequence. Morespecifically, the first known data sequence is inserted in the last 2segments of the 3^(rd) MH block (B3), and the second known data sequencein inserted in the 2^(nd) and 3^(rd) segments of the 4^(th) MH block(B4). Furthermore, the 3^(rd) to 6^(th) known data sequences arerespectively inserted in the last 2 segments of each of the 4^(th),5^(th), 6^(th), and 7^(th) MH blocks (B4, B5, B6, and B7). The 1^(st)and 3^(rd) to 6^(th) known data sequences are spaced apart by 16segments.

FIG. 3 illustrates an RS frame according to an embodiment of the presentinvention.

The RS frame shown in FIG. 3 corresponds to a collection of one or moredata groups. The RS frame is received for each MH frame in a conditionwhere the receiving system receives the FIC and processes the receivedFIC and where the receiving system is switched to a time-slicing mode sothat the receiving system can receive MH ensembles including ESG entrypoints. Each RS frame includes IP streams of each service or ESG, andSMT section data may exist in all RS frames.

The RS frame according to the embodiment of the present inventionconsists of at least one MH transport packet (TP). Herein, the MH TPincludes an MH header and an MH payload.

The MH payload may include mobile service data as well as signalingdata. More specifically, an MH payload may include only mobile servicedata, or may include only signaling data, or may include both mobileservice data and signaling data.

According to the embodiment of the present invention, the MH header mayidentify (or distinguish) the data types included in the MH payload.More specifically, when the MH TP includes a first MH header, thisindicates that the MH payload includes only the signaling data. Also,when the MH TP includes a second MH header, this indicates that the MHpayload includes both the signaling data and the mobile service data.Finally, when MH TP includes a third MH header, this indicates that theMH payload includes only the mobile service data.

In the example shown in FIG. 3, the RS frame is assigned with IPdatagrams (IP datagram 1 and IP datagram 2) for two service types.

Data Transmission Structure

FIG. 4 illustrates a structure of a MH frame for transmitting andreceiving mobile service data according to the present invention. In theexample shown in FIG. 4, one MH frame consists of 5 sub-frames, whereineach sub-frame includes 16 slots. In this case, the MH frame accordingto the present invention includes 5 sub-frames and 80 slots.

Also, in a packet level, one slot is configured of 156 data packets(i.e., transport stream packets), and in a symbol level, one slot isconfigured of 156 data segments. Herein, the size of one slotcorresponds to one half (½) of a VSB field. More specifically, since one207-byte data packet has the same amount of data as a data segment, adata packet prior to being interleaved may also be used as a datasegment. At this point, two VSB fields are grouped to form a VSB frame.

FIG. 5 illustrates an exemplary structure of a VSB frame, wherein oneVSB frame consists of 2 VSB fields (i.e., an odd field and an evenfield). Herein, each VSB field includes a field synchronization segmentand 312 data segments.

The slot corresponds to a basic time unit for multiplexing the mobileservice data and the main service data. Herein, one slot may eitherinclude the mobile service data or be configured only of the mainservice data.

If the first 118 data packets within the slot correspond to a datagroup, the remaining 38 data packets become the main service datapackets. In another example, when no data group exists in a slot, thecorresponding slot is configured of 156 main service data packets.

Meanwhile, when the slots are assigned to a VSB frame, an off-set existsfor each assigned position.

FIG. 6 illustrates a mapping example of the positions to which the first4 slots of a sub-frame are assigned with respect to a VSB frame in aspatial area. And, FIG. 7 illustrates a mapping example of the positionsto which the first 4 slots of a sub-frame are assigned with respect to aVSB frame in a chronological (or time) area.

Referring to FIG. 6 and FIG. 7, a 38^(th) data packet (TS packet #37) ofa 1^(st) slot (Slot #0) is mapped to the 1^(st) data packet of an oddVSB field. A 38^(th) data packet (TS packet #37) of a 2^(nd) slot (Slot#1) is mapped to the 157^(th) data packet of an odd VSB field. Also, a38^(th) data packet (TS packet #37) of a 3^(rd) slot (Slot #2) is mappedto the 1^(st) data packet of an even VSB field. And, a 38^(th) datapacket (TS packet #37) of a 4^(th) slot (Slot #3) is mapped to the157^(th) data packet of an even VSB field. Similarly, the remaining 12slots within the corresponding sub-frame are mapped in the subsequentVSB frames using the same method.

FIG. 8 illustrates an exemplary assignment order of data groups beingassigned to one of 5 sub-frames, wherein the 5 sub-frames configure anMH frame. For example, the method of assigning data groups may beidentically applied to all MH frames or differently applied to each MHframe. Furthermore, the method of assigning data groups may beidentically applied to all sub-frames or differently applied to eachsub-frame. At this point, when it is assumed that the data groups areassigned using the same method in all sub-frames of the corresponding MHframe, the total number of data groups being assigned to an MH frame isequal to a multiple of ‘5’.

According to the embodiment of the present invention, a plurality ofconsecutive data groups is assigned to be spaced as far apart from oneanother as possible within the sub-frame. Thus, the system can becapable of responding promptly and effectively to any burst error thatmay occur within a sub-frame.

For example, when it is assumed that 3 data groups are assigned to asub-frame, the data groups are assigned to a 1^(st) slot (Slot #0), a5^(th) slot (Slot #4), and a 9^(th) slot (Slot #8) in the sub-frame,respectively. FIG. 8 illustrates an example of assigning 16 data groupsin one sub-frame using the above-described pattern (or rule). In otherwords, each data group is serially assigned to 16 slots corresponding tothe following numbers: 0, 8, 4, 12, 1, 9, 5, 13, 2, 10, 6, 14, 3, 11, 7,and 15. Equation 1 below shows the above-described rule (or pattern) forassigning data groups in a sub-frame.

$\begin{matrix}{{j = {( {{4\; i} + 0} )\mspace{14mu}{mod}\mspace{14mu} 16}}{{Herein},\text{}\begin{matrix}{0 = 0} & {{{{if}\mspace{14mu} i} < 4},} \\{0 = 2} & {{{{else}\mspace{14mu}{if}\mspace{14mu} i} < 8},} \\{0 = 1} & {{{{else}\mspace{14mu}{if}\mspace{14mu} i} < 12},} \\{0 = 3} & {{else}.}\end{matrix}}} & {{Equation}\mspace{14mu} 1}\end{matrix}$

Herein, j indicates the slot number within a sub-frame. The value of jmay range from 0 to 15 (i.e., 0≦j≦15). Also, variable i indicates thedata group number. The value of i may range from 0 to 15 (i.e., 0≦i≦15).

In the present invention, a collection of data groups included in a MHframe will be referred to as a “parade”. Based upon the RS frame mode,the parade transmits data of at least one specific RS frame.

The mobile service data within one RS frame may be assigned either toall of regions A/B/C/D within the corresponding data group, or to atleast one of regions A/B/C/D. In the embodiment of the presentinvention, the mobile service data within one RS frame may be assignedeither to all of regions A/B/C/D, or to at least one of regions A/B andregions C/D. If the mobile service data are assigned to the latter case(i.e., one of regions A/B and regions C/D), the RS frame being assignedto regions A/B and the RS frame being assigned to regions C/D within thecorresponding data group are different from one another. According tothe embodiment of the present invention, the RS frame being assigned toregions A/B within the corresponding data group will be referred to as a“primary RS frame”, and the RS frame being assigned to regions C/Dwithin the corresponding data group will be referred to as a “secondaryRS frame”, for simplicity. Also, the primary RS frame and the secondaryRS frame form (or configure) one parade. More specifically, when themobile service data within one RS frame are assigned either to all ofregions A/B/C/D within the corresponding data group, one paradetransmits one RS frame. Conversely, when the mobile service data withinone RS frame are assigned either to at least one of regions A/B andregions C/D, one parade may transmit up to 2 RS frames.

More specifically, the RS frame mode indicates whether a paradetransmits one RS frame, or whether the parade transmits two RS frames.Such RS frame mode is transmitted as the above-described TPC data.

Table 1 below shows an example of the RS frame mode.

TABLE 1 RS frame mode (2 bits) Description 00 There is only one primaryRS frame for all group regions 01 There are two separate RS frames.Primary RS frame for group regions A and B Secondary RS frame for groupregions C and D 10 Reserved 11 Reserved

Table 1 illustrates an example of allocating 2 bits in order to indicatethe RS frame mode. For example, referring to Table 1, when the RS framemode value is equal to ‘00’, this indicates that one parade transmitsone RS frame. And, when the RS frame mode value is equal to ‘01’, thisindicates that one parade transmits two RS frames, i.e., the primary RSframe and the secondary RS frame. More specifically, when the RS framemode value is equal to ‘01’, data of the primary RS frame for regionsA/B are assigned and transmitted to regions A/B of the correspondingdata group. Similarly, data of the secondary RS frame for regions C/Dare assigned and transmitted to regions C/D of the corresponding datagroup.

As described in the assignment of data groups, the parades are alsoassigned to be spaced as far apart from one another as possible withinthe sub-frame. Thus, the system can be capable of responding promptlyand effectively to any burst error that may occur within a sub-frame.

Furthermore, the method of assigning parades may be identically appliedto all MH frames or differently applied to each MH frame. According tothe embodiment of the present invention, the parades may be assigneddifferently for each MH frame and identically for all sub-frames withinan MH frame. More specifically, the MH frame structure may vary by MHframe units. Thus, an ensemble rate may be adjusted on a more frequentand flexible basis.

FIG. 9 illustrates an example of multiple data groups of a single paradebeing assigned (or allocated) to an MH frame. More specifically, FIG. 9illustrates an example of a plurality of data groups included in asingle parade, wherein the number of data groups included in a sub-frameis equal to ‘3’, being allocated to an MH frame.

Referring to FIG. 9, 3 data groups are sequentially assigned to asub-frame at a cycle period of 4 slots. Accordingly, when this processis equally performed in the 5 sub-frames included in the correspondingMH frame, 15 data groups are assigned to a single MH frame. Herein, the15 data groups correspond to data groups included in a parade.Therefore, since one sub-frame is configured of 4 VSB frame, and since 3data groups are included in a sub-frame, the data group of thecorresponding parade is not assigned to one of the 4 VSB frames within asub-frame.

For example, when it is assumed that one parade transmits one RS frame,and that a RS frame encoder (not shown) included in the transmittingsystem performs RS-encoding on the corresponding RS frame, therebyadding 24 bytes of parity data to the corresponding RS frame andtransmitting the processed RS frame, the parity data occupyapproximately 11.37% (=24/(187+24)×100) of the total code word length.Meanwhile, when one sub-frame includes 3 data groups, and when the datagroups included in the parade are assigned, as shown in FIG. 9, a totalof 15 data groups form an RS frame. Accordingly, even when an erroroccurs in an entire data group due to a burst noise within a channel,the percentile is merely 6.67% (=1/15×100). Therefore, the receivingsystem may correct all errors by performing an erasure RS decodingprocess. More specifically, when the erasure RS decoding is performed, anumber of channel errors corresponding to the number of RS parity bytesmay be corrected. By doing so, the receiving system may correct theerror of at least one data group within one parade. Thus, the minimumburst noise length correctable by a RS frame is over 1 VSB frame.

Meanwhile, when data groups of a parade are assigned as shown in FIG. 9,either main service data may be assigned between each data group, ordata groups corresponding to different parades may be assigned betweeneach data group. More specifically, data groups corresponding tomultiple parades may be assigned to one MH frame.

Basically, the method of assigning data groups corresponding to multipleparades is very similar to the method of assigning data groupscorresponding to a single parade. In other words, data groups includedin other parades that are to be assigned to an MH frame are alsorespectively assigned according to a cycle period of 4 slots. At thispoint, data groups of a different parade may be sequentially assigned tothe respective slots in a circular method. Herein, the data groups areassigned to slots starting from the ones to which data groups of theprevious parade have not yet been assigned.

For example, when it is assumed that data groups corresponding to aparade are assigned as shown in FIG. 9, data groups corresponding to thenext parade may be assigned to a sub-frame starting either from the12^(th) slot of a sub-frame. However, this is merely exemplary. Inanother example, the data groups of the next parade may also besequentially assigned to a different slot within a sub-frame at a cycleperiod of 4 slots starting from the 3^(rd) slot.

FIG. 10 illustrates an example of transmitting 3 parades (Parade #0,Parade #1, and Parade #2) to an MH frame. More specifically, FIG. 10illustrates an example of transmitting parades included in one of 5sub-frames, wherein the 5 sub-frames configure one MH frame.

When the 1^(st) parade (Parade #0) includes 3 data groups for eachsub-frame, the positions of each data groups within the sub-frames maybe obtained by substituting values ‘0’ to ‘2’ for i in Equation 1. Morespecifically, the data groups of the 1^(st) parade (Parade #0) aresequentially assigned to the 1^(st), 5^(th), and 9^(th) slots (Slot #0,Slot #4, and Slot #8) within the sub-frame.

Also, when the 2^(nd) parade includes 2 data groups for each sub-frame,the positions of each data groups within the sub-frames may be obtainedby substituting values ‘3’ and ‘4’ for i in Equation 1. Morespecifically, the data groups of the 2^(nd) parade (Parade #1) aresequentially assigned to the 2^(nd) and 12^(th) slots (Slot #1 and Slot#11) within the sub-frame.

Finally, when the 3^(rd) parade includes 2 data groups for eachsub-frame, the positions of each data groups within the sub-frames maybe obtained by substituting values ‘5’ and ‘6’ for i in Equation 1. Morespecifically, the data groups of the 3^(rd) parade (Parade #2) aresequentially assigned to the 7^(th) and 11^(th) slots (Slot #6 and Slot#10) within the sub-frame.

As described above, data groups of multiple parades may be assigned to asingle MH frame, and, in each sub-frame, the data groups are seriallyallocated to a group space having 4 slots from left to right.

Therefore, a number of groups of one parade per sub-frame (NoG) maycorrespond to any one integer from ‘1’ to ‘8’. Herein, since one MHframe includes 5 sub-frames, the total number of data groups within aparade that can be allocated to an MH frame may correspond to any onemultiple of ‘5’ranging from ‘5’ to ‘40’.

FIG. 11 illustrates an example of expanding the assignment process of 3parades, shown in FIG. 10, to 5 sub-frames within an MH frame.

FIG. 12 illustrates a data transmission structure according to anembodiment of the present invention, wherein signaling data are includedin a data group so as to be transmitted.

As described above, an MH frame is divided into 5 sub-frames. Datagroups corresponding to a plurality of parades co-exist in eachsub-frame. Herein, the data groups corresponding to each parade aregrouped by MH frame units, thereby configuring a single parade.

The data structure shown in FIG. 12 includes 3 parades, one ESGdedicated channel (EDC) parade (i.e., parade with NoG=1), and 2 serviceparades (i.e., parade with NoG=4 and parade with NoG=3). Also, apredetermined portion of each data group (i.e., 37 bytes/data group) isused for delivering (or sending) FIC information associated with mobileservice data, wherein the FIC information is separately encoded from theRS-encoding process. The FIC region assigned to each data group consistsof one FIC segments. Herein, each segment is interleaved by MH sub-frameunits, thereby configuring an FIC body, which corresponds to a completedFIC transmission structure. However, whenever required, each segment maybe interleaved by MH frame units and not by MH sub-frame units, therebybeing completed in MH frame units.

Meanwhile, the concept of an MH ensemble is applied in the embodiment ofthe present invention, thereby defining a collection (or group) ofservices. Each MH ensemble carries the same QoS and is coded with thesame FEC code. Also, each MH ensemble has the same unique identifier(i.e., ensemble ID) and corresponds to consecutive RS frames.

As shown in FIG. 12, the FIC segment corresponding to each data groupdescribed service information of an MH ensemble to which thecorresponding data group belongs. When FIC segments within a sub-frameare grouped and deinterleaved, all service information of a physicalchannel through which the corresponding FICs are transmitted may beobtained. Therefore, the receiving system may be able to acquire thechannel information of the corresponding physical channel, after beingprocessed with physical channel tuning, during a sub-frame period.

Furthermore, FIG. 12 illustrates a structure further including aseparate EDC parade apart from the service parade and wherein electronicservice guide (ESG) data are transmitted in the 1^(st) slot of eachsub-frame.

Hierarchical Signaling Structure

FIG. 13 illustrates a hierarchical signaling structure according to anembodiment of the present invention. As shown in FIG. 13, the mobilebroadcasting technology according to the embodiment of the presentinvention adopts a signaling method using FIC and SMT. In thedescription of the present invention, the signaling structure will bereferred to as a hierarchical signaling structure.

Hereinafter, a detailed description on how the receiving system accessesa virtual channel via FIC and SMT will now be given with reference toFIG. 13.

The FIC body defined in an MH transport (M1) identifies the physicallocation of each the data stream for each virtual channel and providesvery high level descriptions of each virtual channel.

Being MH ensemble level signaling information, the service map table(SMT) provides MH ensemble level signaling information. The SMT providesthe IP access information of each virtual channel belonging to therespective MH ensemble within which the SMT is carried. The SMT alsoprovides all IP stream component level information required for thevirtual channel service acquisition.

Referring to FIG. 13, each MH ensemble (i.e., Ensemble 0, Ensemble 1, .. . , Ensemble K) includes a stream information on each associated (orcorresponding) virtual channel (e.g., virtual channel 0 IP stream,virtual channel 1 IP stream, and virtual channel 2 IP stream). Forexample, Ensemble 0 includes virtual channel 0 IP stream and virtualchannel 1 IP stream. And, each MH ensemble includes diverse informationon the associated virtual channel (i.e., Virtual Channel 0 Table Entry,Virtual Channel 0 Access Info, Virtual Channel 1 Table Entry, VirtualChannel 1 Access Info, Virtual Channel 2 Table Entry, Virtual Channel 2Access Info, Virtual Channel N Table Entry, Virtual Channel N AccessInfo, and so on).

The FIC body payload includes information on MH ensembles (e.g.,ensemble_id field, and referred to as “ensemble location” in FIG. 13)and information on a virtual channel associated with the correspondingMH ensemble (e.g., when such information corresponds to amajor_channel_num field and a minor_channel_num field, the informationis expressed as Virtual Channel 0, Virtual Channel 1, . . . , VirtualChannel N in FIG. 13).

The application of the signaling structure in the receiving system willnow be described in detail.

When a user selects a channel he or she wishes to view (hereinafter, theuser-selected channel will be referred to as “channel θ” forsimplicity), the receiving system first parses the received FIC. Then,the receiving system acquires information on an MH ensemble (i.e.,ensemble location), which is associated with the virtual channelcorresponding to channel θ (hereinafter, the corresponding MH ensemblewill be referred to as “MH ensemble θ” for simplicity). By acquiringslots only corresponding to the MH ensemble θ using the time-slicingmethod, the receiving system configures ensemble θ. The ensemble θconfigured as described above, includes an SMT on the associated virtualchannels (including channel θ) and IP streams on the correspondingvirtual channels. Therefore, the receiving system uses the SMT includedin the MH ensemble θ in order to acquire various information on channelθ (e.g., Virtual Channel θ Table Entry) and stream access information onchannel θ (e.g., Virtual Channel θ Access Info). The receiving systemuses the stream access information on channel θ to receive only theassociated IP streams, thereby providing channel θ services to the user.

Fast Information Channel (FIC)

The digital broadcast receiving system according to the presentinvention adopts the fast information channel (FIC) for a faster accessto a service that is currently being broadcasted.

More specifically, the FIC handler 215 of FIG. 1 parses the FIC body,which corresponds to an FIC transmission structure, and outputs theparsed result to the physical adaptation control signal handler 216.

FIG. 14 illustrates an exemplary FIC body format according to anembodiment of the present invention. According to the embodiment of thepresent invention, the FIC format consists of an FIC body header and anFIC body payload.

Meanwhile, according to the embodiment of the present invention, dataare transmitted through the FIC body header and the FIC body payload inFIC segment units. Each FIC segment has the size of 37 bytes, and eachFIC segment consists of a 2-byte FIC segment header and a 35-byte FICsegment payload. More specifically, an FIC body configured of an FICbody header and an FIC body payload, is segmented in units of 35 databytes, which are then carried in at least one FIC segment within the FICsegment payload, so as to be transmitted.

In the description of the present invention, an example of inserting oneFIC segment in one data group, which is then transmitted, will be given.In this case, the receiving system receives a slot corresponding to eachdata group by using a time-slicing method.

The signaling decoder 190 included in the receiving system shown in FIG.1 collects each FIC segment inserted in each data group. Then, thesignaling decoder 190 uses the collected FIC segments to created asingle FIC body. Thereafter, the signaling decoder 190 performs adecoding process on the FIC body payload of the created FIC body, sothat the decoded FIC body payload corresponds to an encoded result of asignaling encoder (not shown) included in the transmitting system.Subsequently, the decoded FIC body payload is outputted to the FIChandler 215. The FIC handler 215 parses the FIC data included in the FICbody payload, and then outputs the parsed FIC data to the physicaladaptation control signal handler 216. The physical adaptation controlsignal handler 216 uses the inputted FIC data to perform processesassociated with MH ensembles, virtual channels, SMTs, and so on.

According to an embodiment of the present invention, when an FIC body issegmented, and when the size of the last segmented portion is smallerthan 35 data bytes, it is assumed that the lacking number of data bytesin the FIC segment payload is completed with by adding the same numberof stuffing bytes therein, so that the size of the last FIC segment canbe equal to 35 data bytes.

However, it is apparent that the above-described data byte values (i.e.,37 bytes for the FIC segment, 2 bytes for the FIC segment header, and 35bytes for the FIC segment payload) are merely exemplary, and will,therefore, not limit the scope of the present invention.

FIG. 15 illustrates an exemplary bit stream syntax structure withrespect to an FIC segment according to an embodiment of the presentinvention.

Herein, the FIC segment signifies a unit used for transmitting the FICdata. The FIC segment consists of an FIC segment header and an FICsegment payload. Referring to FIG. 15, the FIC segment payloadcorresponds to the portion starting from the ‘for’ loop statement.Meanwhile, the FIC segment header may include a FIC_type field, anerror_indicator field, an FIC_seg_number field, and anFIC_last_seg_number field. A detailed description of each field will nowbe given.

The FIC_type field is a 2-bit field indicating the type of thecorresponding FIC.

The error_indicator field is a 1-bit field, which indicates whether ornot an error has occurred within the FIC segment during datatransmission. If an error has occurred, the value of the error_indicatorfield is set to ‘1’. More specifically, when an error that has failed tobe recovered still remains during the configuration process of the FICsegment, the error_indicator field value is set to ‘1’. Theerror_indicator field enables the receiving system to recognize thepresence of an error within the FIC data.

The FIC_seg_number field is a 4-bit field. Herein, when a single FICbody is divided into a plurality of FIC segments and transmitted, theFIC_seg_number field indicates the number of the corresponding FICsegment.

Finally, the FIC_last_seg_number field is also a 4-bit field. TheFIC_last_seg_number field indicates the number of the last FIC segmentwithin the corresponding FIC body.

FIG. 16 illustrates an exemplary bit stream syntax structure withrespect to a payload of an FIC segment according to the presentinvention, when an FIC type field value is equal to ‘0’.

According to the embodiment of the present invention, the payload of theFIC segment is divided into 3 different regions.

A first region of the FIC segment payload exists only when theFIC_seg_number field value is equal to ‘0’. Herein, the first region mayinclude a current_next_indicator field, an ESG_version field, and atransport_stream_id field. However, depending upon the embodiment of thepresent invention, it may be assumed that each of the 3 fields existsregardless of the FIC_seg_number field.

The current_next_indicator field is a 1-bit field. Thecurrent_next_indicator field acts as an indicator identifying whetherthe corresponding FIC data carry MH ensemble configuration informationof an MH frame including the current FIC segment, or whether thecorresponding FIC data carry MH ensemble configuration information of anext MH frame.

The ESG_version field is a 5-bit field indicating ESG versioninformation. Herein, by providing version information on the serviceguide providing channel of the corresponding ESG, the ESG_version fieldenables the receiving system to notify whether or not the correspondingESG has been updated.

Finally, the transport_stream_id field is a 16-bit field acting as aunique identifier of a broadcast stream through which the correspondingFIC segment is being transmitted.

A second region of the FIC segment payload corresponds to an ensembleloop region, which includes an ensemble_id field, an SI_version field,and a num_channel field.

More specifically, the ensemble_id field is an 8-bit field indicatingidentifiers of an MH ensemble through which MH services are transmitted.The MH services will be described in more detail in a later process.Herein, the ensemble_id field binds the MH services and the MH ensemble.

The SI_version field is a 4-bit field indicating version information ofSI data included in the corresponding ensemble, which is beingtransmitted within the RS frame.

Finally, the num_channel field is an 8-bit field indicating the numberof virtual channel being transmitted via the corresponding ensemble.

A third region of the FIC segment payload a channel loop region, whichincludes a channel_type field, a channel_activity field, a CA_indicatorfield, a stand_alone_service_indicator field, a major_channel_num field,and a minor_channel_num field.

The channel_type field is a 5-bit field indicating a service type of thecorresponding virtual channel. For example, the channel_type field mayindicates an audio/video channel, an audio/video and data channel, anaudio-only channel, a data-only channel, a file download channel, an ESGdelivery channel, a notification channel, and so on.

The channel_activity field is a 2-bit field indicating activityinformation of the corresponding virtual channel. More specifically, thechannel_activity field may indicate whether the current virtual channelis providing the current service.

The CA_indicator field is a 1-bit field indicating whether or not aconditional access (CA) is applied to the current virtual channel.

The stand_alone_service_indicator field is also a 1-bit field, whichindicates whether the service of the corresponding virtual channelcorresponds to a stand alone service.

The major_channel_num field is an 8-bit field indicating a major channelnumber of the corresponding virtual channel.

Finally, the minor_channel_num field is also an 8-bit field indicating aminor channel number of the corresponding virtual channel.

Service Table Map

FIG. 17 illustrates an exemplary bit stream syntax structure of aservice map table (hereinafter referred to as “SMT”) according to thepresent invention.

According to the embodiment of the present invention, the SMT isconfigured in an MPEG-2 private section format. However, this will notlimit the scope and spirit of the present invention. The SMT accordingto the embodiment of the present invention includes descriptioninformation for each virtual channel within a single MH ensemble. And,additional information may further be included in each descriptor area.

Herein, the SMT according to the embodiment of the present inventionincludes at least one field and is transmitted from the transmittingsystem to the receiving system.

As described in FIG. 3, the SMT section may be transmitted by beingincluded in the MH TP within the RS frame. In this case, each of the RSframe decoders 170 and 180, shown in FIG. 1, decodes the inputted RSframe, respectively. Then, each of the decoded RS frames is outputted tothe respective RS frame handler 211 and 212. Thereafter, each RS framehandler 211 and 212 identifies the inputted RS frame by row units, so asto create an MH TP, thereby outputting the created MH TP to the MH TPhandler 213.

When it is determined that the corresponding MH TP includes an SMTsection based upon the header in each of the inputted MH TP, the MH TPhandler 213 parses the corresponding SMT section, so as to output the SIdata within the parsed SMT section to the physical adaptation controlsignal handler 216. However, this is limited to when the SMT is notencapsulated to IP datagrams.

Meanwhile, when the SMT is encapsulated to IP datagrams, and when it isdetermined that the corresponding MH TP includes an SMT section basedupon the header in each of the inputted MH TP, the MH TP handler 213outputs the SMT section to the IP network stack 220. Accordingly, the IPnetwork stack 220 performs IP and UDP processes on the inputted SMTsection and, then, outputs the processed SMT section to the SI handler240. The SI handler 240 parses the inputted SMT section and controls thesystem so that the parsed SI data can be stored in the storage unit 290.

The following corresponds to example of the fields that may betransmitted through the SMT.

A table_id field corresponds to an 8-bit unsigned integer number, whichindicates the type of table section. The table_id field allows thecorresponding table to be defined as the service map table (SMT).

A section_syntax_indicator field is a 1-bit field corresponding to anindicator defining the section format of the SLT. For example, thesection format may correspond to MPEG long-form syntax.

A private_indicator field is a 1-bit field indicating whether or not theSMT follows (or is in accordance with) a private section.

A section_length field is a 12-bit field indicating the section lengthof the corresponding SMT.

A transport_stream_id field is a 16-bit field indicating atransport_stream identifier of a physical channel transmitting (ordelivering) the corresponding SMT.

A version_number field is a 5-bit field indicating the version number ofthe corresponding SMT.

A current_next_indicator field is a 1-bit field indicating whether thedata included in subsequent SMT sections are currently applicable.

A section_number field is an 8-bit field indicating the section numberof the corresponding SMT.

A last_section_number field is also an 8-bit field indicating the lastsection number of the corresponding SMT.

An SMT_protocol_version field is an 8-bit field indicating the protocolversion of the corresponding SMT section.

An ensemble_id field is an 8-bit unsigned integer field, whichcorresponds to an ID value associated to the corresponding MH ensemble.Herein, the ensemble_id field may be assigned with a value ranging fromrange ‘0x00’ to ‘0x3F’. It is preferable that the value of theensemble_id field is derived from the parade_id of the TPC data, whichis carried from the baseband processor of MH physical layer subsystem.When the corresponding MH ensemble is transmitted through (or carriedover) the primary RS frame, a value of ‘0’ may be used for the mostsignificant bit (MSB), and the remaining 7 bits are used as theparade_id value of the associated MH parade (i.e., for the leastsignificant 7 bits). Alternatively, when the corresponding MH ensembleis transmitted through (or carried over) the secondary RS frame, a valueof ‘1’ may be used for the most significant bit (MSB).

A num_channels field is an 8-bit field, which specifies the number ofvirtual channels in the corresponding SMT section.

Meanwhile, the SMT according to the embodiment of the present inventionprovides information on a plurality of virtual channels using the ‘for’loop statement.

A major_channel_num field corresponds to an 8-bit field, whichrepresents the major channel number associated with the correspondingvirtual channel. Herein, the major_channel_num field may be assignedwith a value ranging from ‘0x00’ to ‘0xFF’.

A minor_channel_num field corresponds to an 8-bit field, whichrepresents the minor channel number associated with the correspondingvirtual channel. Herein, the minor_channel_num field may be assignedwith a value ranging from ‘0x00’ to ‘0xFF’.

A short_channel_name field indicates the short name of the virtualchannel. The service_id field is a 16-bit unsigned integer number (orvalue), which identifies the virtual channel service.

A service_type field is a 6-bit enumerated type field, which designatesthe type of service carried in the corresponding virtual channel asdefined in Table 2 below.

TABLE 2 0x00 [Reserved] 0x01 MH_digital_television field: the virtualchannel carries television programming (audio, video and optionalassociated data) conforming to ATSC standards. 0x02 MH_audio field: thevirtual channel carries audio programming (audio service and optionalassociated data) conforming to ATSC standards. 0x03 MH_data_only_servicefield: the virtual channel carries a data service conforming to ATSCstandards, but no video or audio component. 0x04 to [Reserved for futureATSC usage] 0xFF

A virtual_channel_activity field is a 2-bit enumerated field identifyingthe activity status of the corresponding virtual channel. When the mostsignificant bit (MSB) of the virtual_channel_activity field is ‘1’, thevirtual channel is active, and when the most significant bit (MSB) ofthe virtual_channel_activity field is ‘0’, the virtual channel isinactive. Also, when the least significant bit (LSB) of thevirtual_channel_activity field is ‘1’, the virtual channel is hidden(when set to 1), and when the least significant bit (LSB) of thevirtual_channel_activity field is ‘0’, the virtual channel is nothidden.

A num_components field is a 5-bit field, which specifies the number ofIP stream components in the corresponding virtual channel.

An IP_version_flag field corresponds to a 1-bit indicator. Morespecifically, when the value of the IP_version_flag field is set to ‘1’,this indicates that a source_IP_address field, avirtual_channel_target_IP_address field, and acomponent_target_IP_address field are IPv6 addresses. Alternatively,when the value of the IP_version_flag field is set to ‘0’, thisindicates that the source_IP_address field, thevirtual_channel_target_IP_address field, and thecomponent_target_IP_address field are IPv4.

A source_IP_address_flag field is a 1-bit Boolean flag, which indicates,when set, that a source IP address of the corresponding virtual channelexist for a specific multicast source.

A virtual_channel_target_IP_address_flag field is a 1-bit Boolean flag,which indicates, when set, that the corresponding IP stream component isdelivered through IP datagrams with target IP addresses different fromthe virtual_channel_target_IP_address. Therefore, when the flag is set,the receiving system (or receiver) uses the component_target_IP_addressas the target_IP_address in order to access the corresponding IP streamcomponent. Accordingly, the receiving system (or receiver) may ignorethe virtual_channel_target_IP_address field included in the num_channelsloop.

The source_IP_address field corresponds to a 32-bit or 128-bit field.Herein, the source_IP_address field will be significant (or present),when the value of the source_IP_address_flag field is set to ‘1’.However, when the value of the source_IP_address_flag field is set to‘0’, the source_IP_address field will become insignificant (or absent).More specifically, when the source_IP_address_flag field value is set to‘1’, and when the IP_version_flag field value is set to ‘0’, thesource_IP_address field indicates a 32-bit IPv4 address, which shows thesource of the corresponding virtual channel. Alternatively, when theIP_version_flag field value is set to ‘1’, the source_IP_address fieldindicates a 128-bit IPv6 address, which shows the source of thecorresponding virtual channel.

The virtual_channel_target_IP_address field also corresponds to a 32-bitor 128-bit field. Herein, the virtual_channel_target_IP_address fieldwill be significant (or present), when the value of thevirtual_channel_target_IP_address_flag field is set to ‘1’. However,when the value of the virtual_channel_target_IP_address_flag field isset to ‘0’, the virtual_channel_target_IP_address field will becomeinsignificant (or absent). More specifically, when thevirtual_channel_target_IP_address_flag field value is set to ‘1’, andwhen the IP_version_flag field value is set to ‘0’, thevirtual_channel_target_IP_address field indicates a 32-bit target IPv4address associated to the corresponding virtual channel. Alternatively,when the virtual_channel_target_IP_address_flag field value is set to‘1’, and when the IP_version_flag field value is set to ‘1’, thevirtual_channel_target_IP_address field indicates a 64-bit target IPv6address associated to the corresponding virtual channel. If thevirtual_channel_target_IP_address field is insignificant (or absent),the component_target_IP_address field within the num_channels loopshould become significant (or present). And, in order to enable thereceiving system to access the IP stream component, thecomponent_target_IP_address field should be used.

The EMT_activity_flag field indicates whether program table informationincluding additional information associated with the correspondingensemble exists. The program table information may describe informationon an additional service that is not described in a service of thecorresponding ensemble in the SMT. Herein, the program table informationwill be referred to as an extended service map table (EMT). And, the EMTwill now be described in more detail. The receiving system (or receiver)uses the EMT_activity_flag field to determine whether an extendedservice map table (EMT), which describes additional service informationassociated with the corresponding SMT, is additionally transmitted inthe broadcast signal. For example, when the EMT_activity_flag fieldvalue is equal to ‘1’, the EMT is transmitted to the correspondingensemble. On the other hand, when the EMT_activity_flag field value isequal to ‘0’, the EMT is not transmitted to the corresponding ensemble.

Meanwhile, the SMT according to the embodiment of the present inventionuses a ‘for’ loop statement in order to provide information on aplurality of components.

Herein, an RTP_payload_type field, which is assigned with 7 bits,identifies the encoding format of the component based upon Table 3 shownbelow. When the IP stream component is not encapsulated to RTP, theRTP_payload_type field shall be ignored (or deprecated).

Table 3 below shows an example of the RTP_payload_type.

TABLE 3 RTP_payload_type Meaning 35 AVC video 36 MH audio 37 to 72[Reserved for future ATSC use]

A component_target_IP_address_flag field is a 1-bit Boolean flag, whichindicates, when set, that the corresponding IP stream component isdelivered through IP datagrams with target IP addresses different fromthe virtual_channel_target_IP_address. Furthermore, when thecomponent_target_IP_address_flag is set, the receiving system (orreceiver) uses the component_target_IP_address field as the target IPaddress for accessing the corresponding IP stream component.Accordingly, the receiving system (or receiver) will ignore thevirtual_channel_target_IP_address field included in the num_channelsloop.

The component_target_IP_address field corresponds to a 32-bit or 128-bitfield. Herein, when the value of the IP_version_flag field is set to‘0’, the component_target_IP_address field indicates a 32-bit targetIPv4 address associated to the corresponding IP stream component. And,when the value of the IP_version_flag field is set to ‘1’, thecomponent_target_IP_address field indicates a 128-bit target IPv6address associated to the corresponding IP stream component.

A port_num_count field is a 6-bit field, which indicates the number ofUDP ports associated with the corresponding IP stream component. Atarget UDP port number value starts from the target_UDP_port_num fieldvalue and increases (or is incremented) by 1. For the RTP stream, thetarget UDP port number should start from the target_UDP_port_num fieldvalue and shall increase (or be incremented) by 2. This is toincorporate RTCP streams associated with the RTP streams.

A target_UDP_port_num field is a 16-bit unsigned integer field, whichrepresents the target UDP port number for the corresponding IP streamcomponent. When used for RTP streams, the value of thetarget_UDP_port_num field shall correspond to an even number. And, thenext higher value shall represent the target UDP port number of theassociated RTCP stream.

A component_level_descriptor ( ) represents zero or more descriptorsproviding additional information on the corresponding IP streamcomponent.

A virtual_channel_level_descriptor ( ) represents zero or moredescriptors providing additional information for the correspondingvirtual channel.

An ensemble_level_descriptor ( ) represents zero or more descriptorsproviding additional information for the MH ensemble, which is describedby the corresponding SMT.

FIG. 18 illustrates an exemplary bit stream syntax structure of an MHaudio descriptor according to the present invention.

When at least one audio service is present as a component of the currentevent, the MH_audio_descriptor ( ) shall be used as acomponent_level_descriptor of the SMT. The MH_audio_descriptor ( ) maybe capable of informing the system of the audio language type and stereomode status. If there is no audio service associated with the currentevent, then it is preferable that the MH_audio_descriptor ( ) isconsidered to be insignificant (or absent) for the current event.

Each field shown in the bit stream syntax of FIG. 18 will now bedescribed in detail.

A descriptor_tag field is an 8-bit unsigned integer having a TBD value,which indicates that the corresponding descriptor is theMH_audio_descriptor ( ).

A descriptor_length field is also an 8-bit unsigned integer, whichindicates the length (in bytes) of the portion immediately following thedescriptor_length field up to the end of the MH_audio_descriptor ( ).

A channel_configuration field corresponds to an 8-bit field indicatingthe number and configuration of audio channels. The values ranging from‘1’ to ‘6’ respectively indicate the number and configuration of audiochannels as given for “Default bit stream index number” in Table 42 ofISO/IEC 13818-7:2006. All other values indicate that the number andconfiguration of audio channels are undefined.

A sample_rate_code field is a 3-bit field, which indicates the samplerate of the encoded audio data. Herein, the indication may correspond toone specific sample rate, or may correspond to a set of values thatinclude the sample rate of the encoded audio data as defined in TableA3.3 of ATSC A/52B.

A bit_rate_code field corresponds to a 6-bit field. Herein, among the 6bits, the lower 5 bits indicate a nominal bit rate. More specifically,when the most significant bit (MSB) is ‘0’, the corresponding bit rateis exact. On the other hand, when the most significant bit (MSB) is ‘0’,the bit rate corresponds to an upper limit as defined in Table A3.4 ofATSC A/53B.

An ISO_(—)639_language_code field is a 24-bit (i.e., 3-byte) fieldindicating the language used for the audio stream component, inconformance with ISO 639.2/B [x]. When a specific language is notpresent in the corresponding audio stream component, the value of eachbyte will be set to ‘0x00’.

FIG. 19 illustrates an exemplary bit stream syntax structure of an MHRTP payload type descriptor according to the present invention.

The MH_RTP_payload_type_descriptor ( ) specifies the RTP payload type.Yet, the MH_RTP_payload_type_descriptor ( ) exists only when the dynamicvalue of the RTP_payload_type field within the num_components loop ofthe SMT is in the range of ‘96’ to ‘127’. TheMH_RTP_payload_type_descriptor ( ) is used as acomponent_level_descriptor of the SMT.

The MH_RTP_payload_type_descriptor translates (or matches) a dynamicRTP_payload_type field value into (or with) a MIME type. Accordingly,the receiving system (or receiver) may collect (or gather) the encodingformat of the IP stream component, which is encapsulated in RTP.

The fields included in the MH_RTP_payload_type_descriptor ( ) will nowbe described in detail.

A descriptor_tag field corresponds to an 8-bit unsigned integer havingthe value TBD, which identifies the current descriptor as theMH_RTP_payload_type_descriptor ( ).

A descriptor_length field also corresponds to an 8-bit unsigned integer,which indicates the length (in bytes) of the portion immediatelyfollowing the descriptor_length field up to the end of theMH_RTP_payload_type_descriptor ( ).

An RTP_payload_type field corresponds to a 7-bit field, which identifiesthe encoding format of the IP stream component. Herein, the dynamicvalue of the RTP_payload_type field is in the range of ‘96’ to ‘127’.

A MIME_type_length field specifies the length (in bytes) of a MIME_typefield.

The MIME_type field indicates the MIME type corresponding to theencoding format of the IP stream component, which is described by theMH_RTP_payload_type_descriptor ( ).

FIG. 20 illustrates an exemplary bit stream syntax structure of an MHcurrent event descriptor according to the present invention.

The MH_current_event_descriptor ( ) shall be used as thevirtual_channel_level_descriptor ( ) within the SMT. Herein, theMH_current_event_descriptor ( ) provides basic information on thecurrent event (e.g., the start time, duration, and title of the currentevent, etc.), which is transmitted via the respective virtual channel.

The fields included in the MH_current_event_descriptor ( ) will now bedescribed in detail.

A descriptor_tag field corresponds to an 8-bit unsigned integer havingthe value TBD, which identifies the current descriptor as theMH_current_event_descriptor ( ).

A descriptor_length field also corresponds to an 8-bit unsigned integer,which indicates the length (in bytes) of the portion immediatelyfollowing the descriptor_length field up to the end of theMH_current_event_descriptor ( ).

An event_id field corresponds to a 16-bit field representing anidentifier for identifying the corresponding event.

A current_event_start_time field corresponds to a 32-bit unsignedinteger quantity. The current_event_start_time field represents thestart time of the current event and, more specifically, as the number ofGPS seconds since 00:00:00 UTC, Jan. 6, 1980.

A current_event_duration field corresponds to a 24-bit field. Herein,the current_event_duration field indicates the duration of the currentevent in hours, minutes, and seconds (wherein the format is in 6 digits,4-bit BCD=24 bits).

A title_length field specifies the length (in bytes) of a title_textfield. Herein, the value ‘0’ indicates that there are no titles existingfor the corresponding event.

The title_text field indicates the title of the corresponding event inevent title in the format of a multiple string structure as defined inATSC A/65C [x].

FIG. 21 illustrates an exemplary bit stream syntax structure of an MHnext event descriptor according to the present invention.

The optional MH_next_event_descriptor ( ) shall be used as thevirtual_channel_level_descriptor ( ) within the SMT. Herein, theMH_next_event_descriptor ( ) provides basic information on the nextevent (e.g., the start time, duration, and title of the next event,etc.), which is transmitted via the respective virtual channel.

The fields included in the MH_next_event_descriptor ( ) will now bedescribed in detail.

A descriptor_tag field corresponds to an 8-bit unsigned integer havingthe value TBD, which identifies the current descriptor as theMH_next_event_descriptor ( ).

A descriptor_length field also corresponds to an 8-bit unsigned integer,which indicates the length (in bytes) of the portion immediatelyfollowing the descriptor_length field up to the end of theMH_next_event_descriptor ( ).

An event_id field corresponds to a 16-bit field representing anidentifier for identifying the corresponding event.

A next_event_start_time field corresponds to a 32-bit unsigned integerquantity. The next_event_start_time field represents the start time ofthe next event and, more specifically, as the number of GPS secondssince 00:00:00 UTC, Jan. 6, 1980.

A next_event_duration field corresponds to a 24-bit field. Herein, thenext_event_duration field indicates the duration of the next event inhours, minutes, and seconds (wherein the format is in 6 digits, 4-bitBCD=24 bits).

A title_length field specifies the length (in bytes) of a title_textfield. Herein, the value ‘0’ indicates that there are no titles existingfor the corresponding event.

The title_text field indicates the title of the corresponding event inevent title in the format of a multiple string structure as defined inATSC A/65C [x].

FIG. 22 illustrates an exemplary bit stream syntax structure of an MHsystem time descriptor according to the present invention.

The MH_system_time_descriptor ( ) shall be used as theensemble_level_descriptor ( ) within the SMT. Herein, theMH_system_time_descriptor ( ) provides information on current time anddate. The MH_system_time_descriptor ( ) also provides information on thetime zone in which the transmitting system (or transmitter) transmittingthe corresponding broadcast stream is located, while taking intoconsideration the mobile/portable characteristics of the MH servicedata.

The fields included in the MH_system_time_descriptor ( ) will now bedescribed in detail.

A descriptor_tag field corresponds to an 8-bit unsigned integer havingthe value TBD, which identifies the current descriptor as theMH_system_time_descriptor ( ).

A descriptor_length field also corresponds to an 8-bit unsigned integer,which indicates the length (in bytes) of the portion immediatelyfollowing the descriptor_length field up to the end of theMH_system_time_descriptor ( ).

A system_time field corresponds to a 32-bit unsigned integer quantity.The system_time field represents the current system time and, morespecifically, as the number of GPS seconds since 00:00:00 UTC, Jan. 6,1980.

A GPS_UTC_offset field corresponds to an 8-bit unsigned integer, whichdefines the current offset in whole seconds between GPS and UTC timestandards. In order to convert GPS time to UTC time, the GPS_UTC_offsetis subtracted from GPS time. Whenever the International Bureau ofWeights and Measures decides that the current offset is too far inerror, an additional leap second may be added (or subtracted).Accordingly, the GPS_UTC_offset field value will reflect the change.

A time_zone_offset_polarity field is a 1-bit field, which indicateswhether the time of the time zone, in which the broadcast station islocated, exceeds (or leads or is faster) or falls behind (or lags or isslower) than the UTC time. When the value of thetime_zone_offset_polarity field is equal to ‘0’, this indicates that thetime on the current time zone exceeds the UTC time. Therefore, atime_zone_offset field value is added to the UTC time value. Conversely,when the value of the time_zone_offset_polarity field is equal to ‘1’,this indicates that the time on the current time zone falls behind theUTC time. Therefore, the time_zone_offset field value is subtracted fromthe UTC time value.

The time_zone_offset field is a 31-bit unsigned integer quantity. Morespecifically, the time_zone_offset field represents, in GPS seconds, thetime offset of the time zone in which the broadcast station is located,when compared to the UTC time.

A daylight_savings field corresponds to a 16-bit field providinginformation on the Summer Time (i.e., the Daylight Savings Time).

A time_zone field corresponds to a (5×8)-bit field indicating the timezone, in which the transmitting system (or transmitter) transmitting thecorresponding broadcast stream is located.

FIG. 23 illustrates segmentation and encapsulation processes of aservice map table (SMT) according to the present invention.

According to the present invention, the SMT is encapsulated to UDP,while including a target IP address and a target UDP port number withinthe IP datagram. More specifically, the SMT is first segmented into apredetermined number of sections, then encapsulated to a UDP header, andfinally encapsulated to an IP header.

In addition, the SMT section provides signaling information on allvirtual channel included in the MH ensemble including the correspondingSMT section. At least one SMT section describing the MH ensemble isincluded in each RS frame included in the corresponding MH ensemble.Finally, each SMT section is identified by an ensemble_id included ineach section.

According to the embodiment of the present invention, by informing thereceiving system of the target IP address and target UDP port number,the corresponding data (i.e., target IP address and target UDP portnumber) may be parsed without having the receiving system to request forother additional information.

For example, when the EMT_activity_flag field value in the SMT is equalto ‘1’ (i.e., when information that EMT is to be transmitted is set up),the EMT linked to the SMT may be transmitted to the ensemble, in whichthe SMT is transmitted. Just as the SMT, the EMT may be transmitted toeach ensemble by sections, which is the transmission unit of the EMT.Herein, the EMT may include a descriptor that describes the additionalservices transmitted by each ensemble. In the example shown in FIG. 24,information are set to indicate that the EMT is being transmitted to theSMT of both Ensemble 1 and Ensemble K. Furthermore, it is also indicatedthat EMT section 1, which is linked to SMT Section 1, and EMT section M,which is linked to SMT Section K, are also transmitted to Ensemble 1 andEnsemble K, respectively. Contents of the EMT will hereinafter bedescribed in detail.

FIG. 24 illustrates a flow chart for accessing a virtual channel usingFIC and SMT according to the present invention.

More specifically, a physical channel is tuned (S501). And, when it isdetermined that an MH signal exists in the tuned physical channel(S502), the corresponding MH signal is demodulated (S503). Additionally,FIC segments are grouped from the demodulated MH signal in sub-frameunits (S504 and S505).

According to the embodiment of the present invention, an FIC segment isinserted in a data group, so as to be transmitted. More specifically,the FIC segment corresponding to each data group described serviceinformation on the MH ensemble to which the corresponding data groupbelongs. When the FIC segments are grouped in sub-frame units and, then,deinterleaved, all service information on the physical channel throughwhich the corresponding FIC segment is transmitted may be acquired.Therefore, after the tuning process, the receiving system may acquirechannel information on the corresponding physical channel during asub-frame period. Once the FIC segments are grouped, in S504 and S505, abroadcast stream through which the corresponding FIC segment is beingtransmitted is identified (S506). For example, the broadcast stream maybe identified by parsing the transport_stream_id field of the FIC body,which is configured by grouping the FIC segments.

Furthermore, an ensemble identifier, a major channel number, a minorchannel number, channel type information, and so on, are extracted fromthe FIC body (S507). And, by using the extracted ensemble information,only the slots corresponding to the designated ensemble are acquired byusing the time-slicing method, so as to configure an ensemble (S508).

Subsequently, the RS frame corresponding to the designated ensemble isdecoded (S509), and an IP socket is opened for SMT reception (S510).

According to the example given in the embodiment of the presentinvention, the SMT is encapsulated to UDP, while including a target IPaddress and a target UDP port number within the IP datagram. Morespecifically, the SMT is first segmented into a predetermined number ofsections, then encapsulated to a UDP header, and finally encapsulated toan IP header. According to the embodiment of the present invention, byinforming the receiving system of the target IP address and target UDPport number, the receiving system parses the SMT sections and thedescriptors of each SMT section without requesting for other additionalinformation (S511).

The SMT section provides signaling information on all virtual channelincluded in the MH ensemble including the corresponding SMT section. Atleast one SMT section describing the MH ensemble is included in each RSframe included in the corresponding MH ensemble. Also, each SMT sectionis identified by an ensemble_id included in each section. The SMT mayinclude information indicating whether or not EMT, which transmitsinformation on additional services, is transmitted to the correspondingensemble.

Furthermore each SMT provides IP access information on each virtualchannel subordinate to the corresponding MH ensemble including each SMT.Finally, the SMT provides IP stream component level information requiredfor the servicing of the corresponding virtual channel.

Therefore, by using the information parsed from the SMT, the IP streamcomponent belonging to the virtual channel requested for reception maybe accessed (S513). Accordingly, the service associated with thecorresponding virtual channel is provided to the user (S514).

If it is determined in Step 512 that the SMT includes informationindicating that an EMT exists in the corresponding ensemble (S515:‘YES’), the EMT may be parsed in the corresponding ensemble so as toacquire the additional information (S516). Thereafter, by using theinformation acquired in Step 516, the additional services, which cannotbe described by the SMT, may be described, and the correspondingadditional services may then be provided.

FIG. 25 illustrates an exemplary bit stream syntax structure of an EMTaccording to another embodiment of the present invention. Theabove-described SMT may describe a stream included in theservice-providing virtual channel and channel information on thecorresponding virtual channel. And, when the EMT_activity_flag field ofthe SMT is set up, an EMT, which is added to the SMT so as to describethe services that are to be provided, is transmitted.

Accordingly, the SMT may enable audio/video/data streams of thebroadcast signal to be swiftly or quickly outputted from the digitalbroadcast receiving system. And, the EMT may either provide moredetailed information on each virtual channel or describe the additionalservices.

Contents of the EMT will now be described in detail.

A table_id field is an 8-bit table identifier, which may be set up as anidentifier for identifying the EMT. A section_syntax_indicator fieldcorresponds to an indicator defining the section format of the EMT. Forexample, the section format may correspond to MPEG long-form syntax.

A Private_indicator field indicates whether or not the EMT follows (oris in accordance with) a private section. A reserved field correspondsto a non-designated field, and the value of the reserved field may, forexample, be set to ‘1’.

A section_length field indicates the section length of the correspondingEMT. A transport_stream_id field represents a transport_stream indicatorof a physical channel through which the corresponding EMT is beingtransmitted. Herein, also, a reserved field corresponds to anon-designated field, and the value of the reserved field may, forexample, be set to ‘1’.

A version_number field indicates the version number of the correspondingEMT. A current_next_indicator field indicates whether the data includedin subsequent EMT sections are currently applicable. A section_numberfield indicates the section number of the corresponding EMT.

A last_section_number field indicates the last section number of thecorresponding EMT. An EMT_protocol_version field indicates the protocolversion of the corresponding EMT section.

An ensemble_id field indicates an identification number of the ensemblewhich the EMT describes. A num_channels field indicates the number ofchannels included in the corresponding ensemble.

A major_channel_number field indicates the major channel number of thecorresponding virtual channel, and a minor_channel_number fieldindicates the minor channel number of the corresponding virtual channel.

A num_components field indicates the number of components included inthe corresponding virtual channel.

The EMT may include a descriptor with respect to each level. Forexample, the EMT may include a descriptor for a component level (i.e.,component_level_descriptor), a descriptor for an event level (i.e.,event_level_descriptor), a descriptor for a virtual channel level (i.e.,virtual_channel_level_descriptor), and a descriptor for an ensemblelevel (i.e., ensemble_level_descriptor).

More specifically, the component_level_descriptor may includeinformation on the corresponding component.

A num_events field indicates a number of events included in an event.

And, the event_level_descriptor may include information on thecorresponding event. Furthermore, the virtual_channel_level_descriptorand ensemble descriptor for each virtual channel may respectivelyinclude information on the corresponding virtual channel and thecorresponding ensemble (i.e., ensemble_level_descriptor).

For example, the SMT describes basic information on a virtual channel ofan ensemble, whereas the EMT may deliver (or transmit) additionalservice information or detailed information on additional service withrespect to the virtual channel included in the corresponding ensemblevia descriptors for each level. The descriptor for the EMT may includeprogram guide information for the virtual channel, informationassociated with data broadcasting, information associated withinteractive services, permission information associated with whether ornot access to each virtual channel has been permitted, and so on.

Furthermore, a descriptor for an audio component among the virtualchannel components shown in FIG. 18, a descriptor for which the virtualchannel describes a current/next event, as shown in FIG. 19 and FIG. 20,and a descriptor describing a system time, as shown in FIG. 22, may beincluded in the EMT so as to be transmitted and received.

Also, the above-described EMT (or SMT according to the second embodimentof the present invention) may be divided into constant units, such assection units. Herein, each of the constant units may describe anensemble.

When an SMT is received, the SI handler 240 of the receiving systemshown in FIG. 1 may parse the SMT. Herein, when the SI handler 240acquires information indicating that an EMT included in the SMT is beingreceived, the SI handler 240 may receive the EMT from the IP networkstack 220. The SI handler 240 may include an EMT parser, which parsesdetailed information on the virtual channel included in the EMT and,then, stores the parsed information in the storage unit 290. The MHmanagement processor 200 reads the information parsed from the EMT fromthe storage unit 290. Then, the MH management processor 200 delivers (orsends) the read information to the MH baseband processor 100 or the MHpresentation processor 300.

For example, when the information parsed from the EMT corresponds toinformation associated with a current or next event, or when theinformation parsed from the EMT corresponds to information associatedwith data broadcasting, the MH presentation processor 300 may controlthe system so that the information associated with an event orinformation associated with data broadcasting, which is delivered to theEMT, can be displayed to the user.

Furthermore, when the additional information parsed from the EMTcorresponds to permission information on the storage or copying ofspecific broadcast data content, the MH management processor 200 maystore or copy the broadcast data content received from a broadcastsignal based upon the corresponding permission information.

For example, when the application manager activates an application foradditional service, such as data broadcasting, and when the additionalservice information transmitted to the EMT is read from the storage unit290, the corresponding additional service information may be used toprovide the additional service to the user.

Therefore, by using the information delivered to the above-described EMT(or SMT according to the second embodiment of the present invention),the receiving system (or receiver) may provide additional serviceinformation, which is associated with the corresponding ensemble,virtual channel, and component of the virtual channel, to the user alongwith the broadcast signal.

As described above, the present invention may provide a servicetransmitted through a virtual channel by using the SMT. The presentinvention may also identify that the EMT is being transmitted from theSMT. Furthermore, the present invention may acquire detailed additionalinformation associated with the component included in the virtualchannel, the event, the virtual channel, and the ensemble from the EMT.Thereafter, the present invention may provide the detailed additionalinformation acquired from the EMT as an additional service.

Meanwhile, by receiving and processing mobile service data for datacasting, the present invention may provide data casting service to theuser. The present invention may transmit mobile service data for datacasting service in a table format. In the description of the presentinvention, such table will be referred to as a data casting table (DCT).Hereinafter, the mobile service data for data casting service will bereferred to as “content” or “multimedia” and “data file” for simplicity.The content may have a single file structure, and a file may be dividedinto at least one fragment. Herein, the file will be assigned to thedata casting table in fragment units, thereby being transmitted.

At this point, the content being included in the DCT and received by thereceiving system may correspond to data synchronized with a mobile A/Vbroadcast program currently being broadcasted or to non-synchronizeddata. If the content corresponds to the data synchronized with a mobileA/V broadcast program, the data casting service may be provided by beinginterconnected with the mobile A/V broadcast program. On the other hand,if the content corresponds to data non-synchronized with a mobile A/Vbroadcast program, the data casting service may be providedindependently.

According to a first embodiment of the present invention, informationassociated with content, which includes identification information foridentifying synchronization status and display information, is includedin the DCT transmitting the corresponding content.

According to a second embodiment of the present invention, informationassociated with content, which includes identification information foridentifying synchronization status and display information, is includedin at least one of an SMT and an EMT in a descriptor format.

First Embodiment

According to a first embodiment of the present invention, content forthe data casting service and information associated with content areincluded in the DCT, thereby being received.

FIG. 26 illustrates an exemplary syntax structure of a data castingtable (DCT) according to the first embodiment of the present invention.Herein, the DCT is configured in an MPEG-2 private section format.However, this will not limit the scope and spirit of the presentinvention. Referring to FIG. 26, the table_ID field indicates that thecorresponding table is a DCT. The section_syntax_indicator field may beset to have a value of ‘1’. This may indicate that a general MPEG-2section syntax may follow the section_length field. Theprivate_indicator field indicates whether or not the DCT is inaccordance with a private section. The section_length field indicatesthe length of the SCT section in byte units. The transport_stream_idfield indicates a transport_stream identifier of a physical channelthrough which the corresponding DCT is being transmitted.

The version_number field indicates the version number of thecorresponding DCT. The current_next_indicator field indicates whether ornot the data included in the following DCT section are currentlyapplicable. The section_number field indicates the section number of thecorresponding DCT. The last_section_number field indicates the lastsection number of a completed DCT. The protocol_version field indicatesthe protocol version of the corresponding DCT. The content_id fieldindicates an identification value for identifying the content beingtransmitted to the corresponding DCT. The content_name field is repeatedas many times as the content_name_length field value, thereby indicatingthe name of the content being transmitted to the corresponding DCT.

The MIME_type( ) field is repeated as many times as the MIME_type_lengthfield value, thereby indicating a MIME type of the content beingtransmitted to the corresponding DCT. The sync_type field indicateswhether or not the content being transmitted to the corresponding DCT issynchronized with the mobile A/V broadcast program. For example, if thesync_type field value is equal to ‘00’, this indicates that the contentis synchronized with the mobile A/V broadcast program. Conversely, ifthe sync_type field value is equal to ‘01’, this indicates that thecontent is not synchronized (or non-synchronized).

When the sync_type field type value is equal to ‘00’, the sync_typefield may include the major_channel_number field, theminor_channel_number field, the now_flag field, and the trigger_durationfield. Herein, the sync_type field may further include a trigger_timefield based upon the now_flag field value. When the sync_type field typevalue is equal to ‘00’, the major_channel_number field indicates a majorchannel number of the mobile A/V broadcast program synchronized with thecontent. Alternatively, when the sync_type field type value is equal to‘00’, the minor_channel_number field indicates a minor channel number ofthe mobile A/V broadcast program synchronized with the content.

The now_flag field indicates a display type of the content received bythe corresponding DCT. For example, when the now_flag field value isequal to ‘1’, the received content is displayed immediately. On theother hand, when the now_flag field value is equal to ‘0’, the receivedcontent is displayed in accordance with a trigger time. When thenow_flag field value is equal to ‘0’, the trigger_time field indicatesthe start time of the current content as the number of GPS seconds since00:00:00 UTC, Jan. 6, 1980. When the sync_type field value is equal to‘00’, the trigger_duration field indicates the display duration time ofthe received content in ms units. For example, when the now_flag fieldvalue is equal to ‘1’, the received content is immediately displayed,and the duration time of the display is maintained in accordance withthe trigger_duration field value. Alternatively, when the now_flag fieldvalue is equal to ‘0’, the received content is displayed at the timeindicated by the trigger_time field value, and the duration time of thedisplay is maintained in accordance with the trigger_duration fieldvalue.

The expire_time field is included, when the sync_type field value isequal to ‘01’. More specifically, when the sync_type field value isequal to ‘01’, the expire_time field indicates that the content receivedby the DCT is deleted by force. The URI_flag field indicates whether acontent position is designated by a uniform resource identifier (URI).For example, when the URI_flag field value is equal to ‘1’, thisindicates that the position of the content is designated by the URI. Onthe other hand, when the URI_flag field value is equal to ‘0’, thisindicates that the corresponding content is carried in acontent_raw_data field so as to be delivered (or transmitted).

When the URI_flag field value is equal to ‘1’, the URI_length fieldindicates the length of a URI text. Herein, the URI_text ( ) fieldindicates the URI of the position wherein the corresponding content islocated. When the URI_flag field value is equal to ‘0’, thecontent_length field indicates the length of the content_raw_data field.And, in the content_raw_data actual content is fragmented. According tothe first embodiment of the present invention, the now_flag field, thetrigger_time field, the trigger_duration field, and the expire_timefield will be collectively referred to as “display information”.

Second Embodiment

According to a second embodiment of the present invention, content forthe data casting service and information associated with content areincluded in the DCT, thereby being received. Herein, thecontent-associated information is included in at least one of the SMT ofFIG. 17 and the EMT of FIG. 26 in a descriptor format, thereby beingreceived. According to the second embodiment of the present invention,the above-described descriptor will be referred to as the data castdescriptor. FIG. 27 illustrates an exemplary syntax structure of a datacast descriptor MH_DataCast_descriptor( ) according to the secondembodiment of the present invention.

Referring to FIG. 27, the descriptor_tag field indicates that thecorresponding descriptor is a data cast descriptorMH_DataCast_descriptor ( ). The descriptor_length field indicates theindicates the length (in bytes) of the portion immediately following thedescriptor_length field up to the end of the MH_DataCast_descriptor ( ).The content_id field indicates an identification value for identifying(or distinguishing) the content being transmitted to the DCT. Morespecifically, the content_id field value is used as link information forlinking the information associated with the corresponding content to theDCT transmitting the corresponding content. Therefore, the content_idfield value is also included in the DCT, which transmits thecorresponding content. The content_id field of the DCT has the samefield value as that of the content_id field of theMH_DataCast_descriptor ( ).

The content_name field is repeated as many times as thecontent_name_length field value, thereby indicating the name of thecontent being transmitted to the corresponding DCT. The MIME_type( )field is repeated as many times as the MIME_type_length field value,thereby indicating a MIME type of the content being transmitted to thecorresponding DCT. The sync_type field indicates whether or not thecontent being transmitted to the corresponding DCT is synchronized withthe mobile A/V broadcast program. For example, if the sync_type fieldvalue is equal to ‘00’, this indicates that the content is synchronizedwith the mobile A/V broadcast program. Conversely, if the sync_typefield value is equal to ‘01’, this indicates that the content is notsynchronized (or non-synchronized).

When the sync_type field type value is equal to ‘00’, the sync_typefield may include the now_flag field and the trigger_duration field.Herein, the sync_type field may further include a trigger_time fieldbased upon the now_flag field value. When the sync_type field value isequal to ‘00’, the now_flag field indicates a display type of thecontent received by the corresponding DCT. For example, when thenow_flag field value is equal to ‘1’, the received content is displayedimmediately. On the other hand, when the now_flag field value is equalto ‘0’, the received content is displayed in accordance with a triggertime. When the now_flag field value is equal to ‘0’, the trigger_timefield indicates the start time of the current content as the number ofGPS seconds since 00:00:00 UTC, Jan. 6, 1980.

When the sync_type field value is equal to ‘00’, the trigger_durationfield indicates the display duration time of the received content in msunits. For example, when the now_flag field value is equal to ‘1’, thereceived content is immediately displayed, and the duration time of thedisplay is maintained in accordance with the trigger_duration fieldvalue. Alternatively, when the now_flag field value is equal to ‘0’, thereceived content is displayed at the time indicated by the trigger_timefield value, and the duration time of the display is maintained inaccordance with the trigger_duration field value. The expire_time fieldis included, when the sync_type field value is equal to ‘01’. Morespecifically, when the sync_type field value is equal to ‘01’, theexpire_time field indicates that the content received by the DCT isdeleted by force.

FIG. 28 illustrates an exemplary syntax structure of a data castingtable (DCT) according to the second embodiment of the present invention.Herein, the DCT is configured in an MPEG-2 private section format.However, this will not limit the scope and spirit of the presentinvention. Referring to FIG. 28, the table_ID field indicates that thecorresponding table is a DCT. The section_syntax_indicator field may beset to have a value of ‘1’. This may indicate that a general MPEG-2section syntax may follow the section_length field. Theprivate_indicator field indicates whether or not the DCT is inaccordance with a private section. The section_length field indicatesthe length of the DCT section in byte units. The transport_stream_idfield indicates a transport_stream identifier of a physical channelthrough which the corresponding DCT is being transmitted.

The version_number field indicates the version number of thecorresponding DCT. The current_next_indicator field indicates whether ornot the data included in the following DCT section are currentlyapplicable. The section_number field indicates the section number of thecorresponding DCT. The last_section_number field indicates the lastsection number of a completed DCT. The protocol_version field indicatesthe protocol version of the corresponding DCT. The content_id fieldindicates an identification value for identifying the content beingtransmitted to the corresponding DCT.

As described above, the content_id field value is used as linkinformation for linking the information associated with thecorresponding content to the data cast descriptor transmitting thecorresponding content. More specifically, the information associatedwith the content is required for extracting and processing the contentreceived through the DCT. Accordingly, the content_id field value isused as information for searching the data cast descriptor, whichtransmits the information associated with the corresponding content.

The URI_flag field indicates whether or not the position of the contentis designated by using the URI. For example, when the URI_flag fieldvalue is equal to ‘1’, this indicates that the position of the contentis designated by the URI. Alternatively, when the URI_flag field valueis equal to ‘0’, this indicates that the corresponding content iscarried in the content_raw_data field, thereby being transmitted. Whenthe URI_flag field value is equal to ‘1’, the URI_length field indicatesthe length of the URI text. Herein, the URI_text ( ) field indicates theURI of the position where the content is located. When the URI_flagfield value is equal to ‘0’, the content_length field indicates thelength of the content_raw_data field. Actual content is fragmented inthe content_raw_data field.

The mobile A/V broadcast program may correspond to a mobileaudio-specific broadcast program, or to a mobile video-specificbroadcast program, or to a mobile audio/video-integrated broadcastprogram.

For example, when the mobile A/V broadcast program corresponds to amobile audio-specific broadcast program, content including still imagesis delivered through the DCT. Accordingly, while listening to the audiocontent, the user may be provided with background images, such as studioimages, traffic information, weather forecast, stock information,lyrics, music album cover, and so on through the display screen.Furthermore, by sequentially and continuously delivering still imagesthrough the DCT, the images may be provided to the user in a slideshowmode.

Alternatively, in case of music programs, by delivering contentsincluding the music currently being broadcasted through the DCT in anmp3 file format, the corresponding content may be executed (or played)later on. The content according to the present invention may also beapplied in a variety of other data broadcast programs. Morespecifically, the content may be equally applied in mobilevideo-specific broadcast programs or in mobile audio/video-integratedbroadcast programs.

FIG. 29 illustrates a background image showing an audio output powerstatus on a mobile audio transmission screen. Thus, the user may be ableto verify the output power status of the audio content that is currentlybeing played.

FIG. 30 illustrates a background image showing studio images on themobile audio transmission screen. Thus, the user may be informed of theambience of the studio via which the audio content is being provided.

FIG. 31 illustrates a background image showing a music album cover onthe mobile audio transmission screen. Thus, the user may be able to viewthe music album cover image of the song, which the user is listening to.

FIG. 32 illustrates a background image showing traffic information onthe mobile audio transmission screen. Thus, the user may be providedwith traffic information while listening to his/her music program.

FIG. 33 illustrates a background image showing cooking information onthe mobile audio transmission screen. Thus, the user may be providedwith cooking information while listening to his/her music program.

If background images including at least one of the images shown in FIG.29 to FIG. 33 are delivered (or transmitted) through the DCT at aconstant interval, since the images may switch in accordance with theconstant interval, the present invention may provide the images to theuser in a slideshow format.

FIG. 34 illustrates a flow chart of a data casting service methodaccording to an embodiment of the present invention. Particularly, FIG.34 illustrates a data casting service method that can be applied whencontent and information associated with the content are received throughthe DCT shown in FIG. 26. More specifically, when a DCT section isreceived (S701), at least one DCT section is collected so as toconfigure a complete DCT (S702). Herein, the table_id field, thesection_number field, and the last_section_number field within the DCTmay indicate whether a single DCT is configured of a single DCT sectionor multiple DCT section. When the DCT is completed, in step 702, thecontent_id field, the content_name field, the MIME_type field, thesync_type field of the DCT are parsed, so that content identificationinformation (content_id), content name (content_name), MIME typeinformation (MIME_type), and synchronization identification information(sync_type) can be acquired (S703). When the synchronizationidentification information indicates that the content received by theDCT is synchronized with the mobile A/V broadcast program, (i.e., whenthe sync_type field value is equal to ‘00’) (S704), a major channelnumber (major_channel_number) and a minor channel number(minor_channel_number) of the mobile A/V broadcast program synchronizedwith the corresponding content are acquired (S705).

Then, the system verifies whether or not the major channel number(major_channel_number) and the minor channel number(minor_channel_number), which are acquired in step 705, are identical tothe mobile A/V broadcast program that is currently being viewed (S706).If it is determined that the data are identical to one another, thesystem verifies whether the URI_flag field value within the DCT is equalto ‘1’, i.e., whether the position of the content is designated by theURI (S707). In step 707, when the URI_flag field value is equal to ‘1’(i.e., when the position of the content is designated by the URI), theURI_length field and the URI_text ( ) field are parsed so that thecorresponding content can be acquired from the designated URI (S708).Also, in step 707, when the URI_flag field value is equal to ‘0’ (i.e.,when the position of the content is not designated by the URI), thecontent_length field and the content_raw_data field are parsed so thatthe content transmitted to the DCT can be acquired.

At this point, the content configured of a single file is divided intoat least one fragment. Herein, since each fragment unit is included inthe DCT and received, the fragments corresponding to a content file arecollected to configure the content file. Also, the system verifieswhether the now_flag field value of the DCT is equal to ‘0’ (S710). Forexample, when the now_flag field value is equal to ‘1’, the receivedcontent is immediately displayed. And, when the now_flag field value isequal to ‘0’, the received content is displayed in accordance with thetrigger time. Therefore, in step 710, when the now_flag field value isequal to ‘1’, the content acquired in step 708 or in step 709 isimmediately displayed. Thereafter, the duration of the content displayis maintained in accordance with the trigger_duration field value(S711). Also, in step 710, when the now_flag field value is equal to‘0’, the content acquired in step 708 or in step 709 is displayed at thetime indicated by the trigger_time field value. Thereafter, the durationof the content display is maintained in accordance with thetrigger_duration field value (S712).

Meanwhile, in step 704, when the synchronization identificationinformation indicates that the content received by the DCT is notsynchronized with the mobile A/V broadcast program, (i.e., when thesync_type field value is equal to ‘01’), the system verifies whether ornot the URI_flag field value within the DCT is equal to ‘1’ (i.e.,whether the position of the content is designated by the URI) (S713). Instep 713, when the URI_flag field value is equal to ‘1’ (i.e., when theposition of the content is designated by the URI), the URI_length fieldand the URI_text ( ) field are parsed so that the corresponding contentcan be acquired from the designated URI (S714). Also, in step 713, whenthe URI_flag field value is equal to ‘0’ (i.e., when the position of thecontent is not designated by the URI), the content_length field and thecontent_raw_data field are parsed so that the content transmitted to theDCT can be acquired (S715). Furthermore, after storing the contentacquired in step 714 or step 715 in a non-volatile memory (S716), whenthe time designated by the expire_time field value within the DCT isexpired (or passed), the corresponding content is deleted from thenon-volatile memory (S717). At this point, when the user inputs arequest within the time designated by the expire_time field value, thecorresponding content is read and outputted from the non-volatile memoryso as to be processed and displayed to the display screen.

The digital broadcast receiving system of FIG. 1 may further include aDCT handler processing content for the above-described data castingservice. If the DCT is transmitted via an IP-based channel, the DCThandler may be provided between the IP network stack 220 and the storageunit 290. The operation of the DCT handler will be described in detaillater on. Furthermore, if the content for the data casting service isreceived via an IP-based channel, the digital broadcast receiving systemmay further include a URI handler acquiring and processing content fromthe designated URI. Herein, the URI handler may also be provided betweenthe IP network stack 220 and the storage unit 290.

FIG. 35 illustrates a block view showing the structure of a receivingsystem according to another embodiment of the present invention. Thereceiving system shown in FIG. 35 includes a host 800, a basebandprocessor 801, an RS frame handler 802, an A/V decoder 803, a displaymodule 804, an FIC handler 806, an SMT handler 807, a channel/servicemap database (DB) 808, a DCT handler 809, a URI handler 810, a contentstorage unit 811, and a content processor 812. The host 800 may be aCPU, or an operation controller 110 shown in FIG. 1, or a physicaladaptation control signal handler 216. The baseband processor 100 shownin FIG. 1 may be directly applied as the baseband processor 801 withoutmodification. The SMT handler 807 may include an EMT handler. Morespecifically, the RS frame demodulated and error-corrected by thebaseband processor 801 is outputted to the RS frame handler 802, and theFIC is outputted to the FIC handler 806.

The FIC handler 806 parses the FIC received from the baseband processor801. Then, the FIC handler 806 stores the FIC data, which correspond tothe parsed result, in the channel/service map DB 808 through the host800. The channel/service map DB 808 stores information on all servicemaps that can be accessed by the receiving system. Thereafter, thechannel/service map DB 808 provides the corresponding information to thehost 800 when requested. Herein, the term “access” refers to whether ornot the receiving system can recognize the presence of a service,regardless of whether the receiving system can consume the service ornot. However, when a service provider provides a service designated onlyto a specific type of receiver (or receiving system), receiving systemsother than the designated receiver type may not be able to access theservice that is being provided. Herein, the channel/service map DB 808may correspond to the storage unit 290 of FIG. 1.

The RS frame handler 802 identifies (or distinguishes) a mobile audiostream and a mobile video stream from the RS frame transmitted from thebaseband processor 801 at a constant time interval (e.g., MH frame)determined by the host 800 and respectively outputs the identifiedmobile audio/video streams to the A/V decoder 803. When only the mobileaudio stream is outputted from the RS frame handler 802, the A/V decoder803 performs audio decoding using an audio decoding algorithm. And, whenonly the mobile video stream is outputted from the RS frame handler 802,the A/V decoder 803 performs video decoding using a video decodingalgorithm. Finally, when both the mobile audio stream and the mobilevideo stream are outputted from the RS frame handler 802, the A/Vdecoder 803 performs audio decoding and video decoding using the audiodecoding algorithm and the video decoding algorithm, respectively.Thereafter, the audio and/or video data decoded by the A/V decoder 803are provided to the user through a display screen and/or speaker of thedisplay module 804.

Additionally, when an SMT section is included in the RS frame, the RSframe handler 802 outputs the SMT section to the SMT handler 807. If theEMT section is included in the SMT section, the EMT section is alsooutputted to the SMT handler 807. The SMT handler 807 collects (orgathers) at least one SMT section so as to complete an SMT. Thereafter,the SMT handler 807 parses the completed SMT and stores the parsedresult in the channel/service map DB 808 through the host 800. When theSMT is parsed, MH ensemble level signaling information, IP accessinformation on each virtual channel belonging to the corresponding MHensemble including each SMT, and IP stream component level informationrequired for servicing (or providing) the corresponding virtual channelmay be acquired. Furthermore, the SMT handler 807 collects (or gathers)at least one EMT section so as to complete an EMT. Thereafter, the SMThandler 807 parses the completed EMT and stores the parsed result in thechannel/service map DB 808 through the host 800.

If a data cast descriptor shown in FIG. 27 is included in the parsed SMTor EMT, the SMT handler 807 outputs the data cast descriptor to the DCThandler 809. Also, if a DCT section is included in the RS frame, the RSframe handler 802 outputs the DCT section to the DCT handler 809. TheDCT handler 809 collects at least one DCT section, so as to complete asingle DCT. Thereafter, the DCT handler 809 parses the completed DCT.Herein, the content for data casting service may be included in the DCTand received. The information associated with the content may either beincluded in the DCT and then received, or be included in the SMT or EMTas the data cast descriptor and then received.

Accordingly, when the content for the data casting service and theinformation associated with the content are included in the DCT and thenreceived, according to the first embodiment of the present invention,the DCT is parsed so as to extract the content and informationassociated with the content. Then, based upon the extracted informationassociated with the content, the corresponding content is eitherimmediately displayed on the display screen or displayed on the displayscreen at a designated time.

Alternatively, when the content for the data casting service isincluded, and when the information associated with the content isincluded in the SMT or EMT as the data cast descriptor and thenreceived, according to the second embodiment of the present invention,the data cast descriptor is parsed so as to extract informationassociated with the content, and the DCT is parsed so as to extract thecontent. Herein, the content_id field value may be used as informationfor linking the data cast descriptor to the DCT. Also, based upon theinformation associated with the extracted information, the correspondingcontent is immediately displayed on the display screen during apredetermined trigger duration period. Alternatively, the correspondingcontent is displayed on the display screen at a designated trigger timeduring a predetermined trigger duration period.

Meanwhile, when the URI_flag field value in the DCT is equal to ‘1’(i.e., when the position of the content is designated by the URI), thisindicates that the content for the data casting service is received viaan IP-based channel having the URI. In this case, based upon the controlof the host 800, the URI handler 810 acquires content of the designatedURI from the RS frame, thereby outputting the acquired content to theDCT handler 809. Based upon the information associated the contentextracted from any one of the tables DCT, SMT, and EMT, the DCT handler809 either immediately displays the corresponding content on the displayscreen or displays the content on the display screen at a designatedtime.

More specifically, among the information associated with the content,when the display type information (i.e., now_flag field) designatesimmediate display, the corresponding content is inputted to the contentprocessor 812, so as to be processed to fit the required display format.Afterwards, the processed content is outputted to the display screenthrough the display module 804 during the predetermined triggerduration. Meanwhile, when the display type information (i.e., now_flagfield) designates a specific display trigger time, the correspondingcontent is stored in the content storage unit 811, which is anon-volatile memory unit. Subsequently, at the designated displaytrigger time, the stored content is inputted to the content processor812, so as to be processed to fit the required display format.Thereafter, the processed content is outputted to the display screenthrough the display module 804 during the predetermined triggerduration.

It will be apparent to those skilled in the art that variousmodifications and variations can be made in the present inventionwithout departing from the spirit or scope of the inventions. Thus, itis intended that the present invention covers the modifications andvariations of this invention provided they come within the scope of theappended claims and their equivalents.

1. A method of processing broadcast data in a broadcast receiver, themethod comprising: receiving a broadcast signal, the broadcast signalcomprising mobile service data, a service map table (SMT) includingaccess information of the mobile service data, known data sequences,fast information channel (FIC) data, and transmission parameter channel(TPC) data, wherein the FIC data includes information for rapid mobileservice acquisition, and wherein the TPC data includes FIC versioninformation for indicating an update of the FIC data; buildingReed-Solomon (RS) frames including the mobile service data from thereceived broadcast signal, the RS frames belonging to an ensemble, theensemble including the SMT; obtaining the SMT from the ensemble; andprocessing the mobile service data based on the access information ofthe SMT, wherein a size of at least one of the RS frames is L (rows)×N(column size of a payload of the RS frame) bytes, each row having anM-byte header leaving the rest of the row available for data, whereinthe data in the rows are packed into the rows end-to-end, with possiblewrapping around at the end of each row to the next row, wherein L, M,and N are integers, and wherein the FIC data and the SMT further includean ensemble identifier for identifying the ensemble, respectively. 2.The method of claim 1, wherein the FIC data and the TPC data arepositioned between a first known data sequence and a second known datasequence of the known data sequences.
 3. The method of claim 1, whereinat least two of the known data sequences are spaced 16 segments apartand have different lengths.
 4. The method of claim 1, wherein the headerincludes at least one of type information indicating a type of data inthe row, information indicating whether or not an error is included inthe row, and information indicating whether or not stuffing bytes areincluded in the row.
 5. The method of claim 4, further comprisingdetermining a type of the mobile service data included in the row basedupon the type information included in the header.
 6. A broadcastreceiver comprising: a tuner for receiving a broadcast signal, thebroadcast signal comprising mobile service data, a service map table(SMT) including access information of the mobile service data, knowndata sequences, fast information channel (FIC) data, and transmissionparameter channel (TPC) data, wherein the FIC data includes informationfor rapid mobile service acquisition, and wherein the TPC data includesFIC version information for indicating an update of the FIC data; adecoder for building Reed-Solomon (RS) frames including the mobileservice data from the received broadcast signal, the RS frames belongingto an ensemble, the ensemble including the SMT; a handler for obtainingthe SMT from the ensemble; and a processor for processing the mobileservice data based on the access information of the SMT, wherein a sizeof at least one of the RS frames is L (rows)×N (column size of a payloadof the RS frame) bytes, each row having an M-byte header leaving therest of the row available for data, wherein the data in the rows arepacked into the rows end-to-end, with possible wrapping around at theend of each row to the next row, wherein L, M, and N are integers, andwherein the FIC data and the SMT further include an ensemble identifierfor identifying the ensemble, respectively.
 7. The broadcast receiver ofclaim 6, wherein the FIC data and the TPC data are positioned between afirst known data sequence and a second known data sequence of the knowndata sequences.
 8. The broadcast receiver of claim 6, wherein at leasttwo of the known data sequences are spaced 16 segments apart and havedifferent lengths.
 9. The broadcast receiver of claim 6, wherein theheader includes at least one of type information indicating a type ofdata in the row, information indicating whether or not an error isincluded in the row, and information indicating whether or not stuffingbytes are included in the row.
 10. The broadcast receiver of claim 9,wherein the decoder determines a type of the mobile service dataincluded in the row based upon the type information included in theheader.
 11. A method of processing broadcast data in a broadcasttransmitter, the method comprising: performing, by a Reed Solomon (RS)encoder, RS encoding and Cyclic Redundancy Check (CRC) encoding onmobile service data to build RS frames, the RS frames belonging to anensemble, wherein the ensemble includes a service map table (SMT)including access information of the mobile service data; mapping each ofthe RS frames into a plurality of groups, wherein each group includes aportion of data included in a corresponding RS frame, known datasequences, fast information channel (FIC) data, and transmissionparameter channel (TPC) data, wherein the FIC data includes informationfor rapid mobile service acquisition, and wherein the TPC data includesFIC version information for indicating an update of the FIC data; andtransmitting a broadcast signal including the plurality of groups,wherein a size of at least one of the RS frames is L (rows)×N (columnsize of a payload of the RS frame) bytes, each row having an M-byteheader leaving the rest of the row available for data, wherein the datain the rows are packed into the rows end-to-end, with possible wrappingaround at the end of each row to the next row, wherein L, M, and N areintegers, and wherein the FIC data and SMT further include an ensembleidentifier for identifying the ensemble, respectively.
 12. The method ofclaim 11, wherein the FIC data and the TPC data are positioned between afirst known data sequence and a second known data sequence of the knowndata sequences.
 13. The method of claim 11, wherein at least two of theknown data sequences are spaced 16 segments apart and have differentlengths.
 14. The method of claim 11, wherein the header includes typeinformation indicating a type of data in the row and informationindicating whether or not an error is included in the row.
 15. Themethod of claim 14, wherein the header further includes informationindicating whether or not stuffing bytes are included in the row.
 16. Abroadcast transmitter comprising: a Reed Solomon (RS) encoder forperforming RS encoding and Cyclic Redundancy Check (CRC) on mobileservice data to build RS frames, the RS frames belonging to an ensemble,wherein the ensemble includes a service map table (SMT) including accessinformation of the mobile service data, wherein each of the RS frames ismapped into a plurality of groups, wherein each group includes a portionof data included in a corresponding RS frame, known data sequences, fastinformation channel (FIC) data, and transmission parameter channel (TPC)data, wherein the FIC data includes information for rapid mobile serviceacquisition, and wherein the TPC data includes FIC version informationfor indicating an update of the FIC data; and a transmission unit fortransmitting a broadcast signal including the plurality of groups,wherein a size of at least one of the RS frames is L (rows)×N (columnsize of a payload of the RS frame) bytes, each row having an M-byteheader leaving the rest of the row available for data, wherein the datain the rows are packed into the rows end-to-end, with possible wrappingaround at the end of each row to the next row, wherein L, M, and N areintegers, and wherein the FIC data and the SMT further include anensemble identifier for identifying the ensemble, respectively.
 17. Thebroadcast transmitter of claim 16, wherein the FIC data and the TPC dataare positioned between a first known data sequence and a second knowndata sequence of the known data sequences.
 18. The broadcast transmitterof claim 16, wherein at least two of the known data sequences are spaced16 segments apart and have different lengths.
 19. The broadcasttransmitter of claim 16, wherein the header includes type informationindicating a type of data in the row and information indicating whetheror not an error is included in the row.
 20. The broadcast transmitter ofclaim 19, wherein the header further includes information indicatingwhether or not stuffing bytes are included in the row.